Skip to content

remove enable community extensions flag #5167

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

remove enable community extensions flag #5167

wants to merge 2 commits into from

Conversation

pablochacin
Copy link
Contributor

@pablochacin pablochacin commented Sep 10, 2025 •
edited
Loading

What?

Removes the enable community extensions flag and the need to adjust the build service's URL to select the oss catalog when they were enabled.

Why?

After alll extensions were integrated into a single catalog that includes both official and community extensions, and all these extensions are supported in GCK6, there's no need to explicitly enable community extensions.

Checklist

  • I have performed a self-review of my code.
  • I have commented on my code, particularly in hard-to-understand areas.
  • I have added tests for my changes.
  • I have run linter and tests locally (make check) and all pass.

Checklist: Documentation (only for k6 maintainers and if relevant)

Please do not merge this PR until the following items are filled out.

  • I have added the correct milestone and labels to the PR.
  • I have updated the release notes: link
  • I have updated or added an issue to the k6-documentation: grafana/k6-docs#NUMBER if applicable
  • I have updated or added an issue to the TypeScript definitions: grafana/k6-DefinitelyTyped#NUMBER if applicable

Related PR(s)/Issue(s)

Closes https://github.com/grafana/k6-cloud/issues/3747
@pablochacin pablochacin temporarily deployed to azure-trusted-signing September 10, 2025 16:16 — with GitHub Actions Inactive
@pablochacin pablochacin temporarily deployed to azure-trusted-signing September 10, 2025 16:18 — with GitHub Actions Inactive
@pablochacin pablochacin marked this pull request as ready for review September 10, 2025 18:52
@pablochacin pablochacin requested a review from a team as a code owner September 10, 2025 18:52
@pablochacin pablochacin requested review from inancgumus and oleiade and removed request for a team September 10, 2025 18:52
@pablochacin pablochacin added the breaking change for PRs that need to be mentioned in the breaking changes section of the release notes label Sep 16, 2025
@codebien codebien self-requested a review October 7, 2025 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change for PRs that need to be mentioned in the breaking changes section of the release notes
2 participants
@pablochacin @inancgumus