Skip to content

Drop ExporterType option from OTEL output - #5754

Merged
joanlopez merged 3 commits into
masterfrom
v2-drop-otel-exportertype
Apr 9, 2026
Merged

Drop ExporterType option from OTEL output#5754
joanlopez merged 3 commits into
masterfrom
v2-drop-otel-exportertype

Conversation

@joanlopez

Copy link
Copy Markdown
Contributor

What?

Basically, what the title says.

Why?

As said in #5348, after some k6 releases where the ExporterType option was already considered deprecated, it's time to finally drop it and only leave the support for the standard ExporterProtocol.

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)

@joanlopez
joanlopez requested a review from a team as a code owner March 24, 2026 11:49
@joanlopez
joanlopez requested review from mstoykov and szkiba and removed request for a team March 24, 2026 11:49
@joanlopez joanlopez self-assigned this Mar 24, 2026
@joanlopez joanlopez added the breaking change for PRs that need to be mentioned in the breaking changes section of the release notes label Mar 24, 2026
@joanlopez
joanlopez requested a review from codebien March 24, 2026 11:49
@joanlopez joanlopez added the documentation-needed A PR which will need a separate PR for documentation label Mar 24, 2026
@joanlopez joanlopez modified the milestones: v2.0.0, v2.0.0-rc1 Mar 24, 2026
@joanlopez
joanlopez temporarily deployed to azure-trusted-signing March 24, 2026 11:55 — with GitHub Actions Inactive
@joanlopez
joanlopez temporarily deployed to azure-trusted-signing March 24, 2026 11:57 — with GitHub Actions Inactive
szkiba
szkiba previously approved these changes Mar 25, 2026
@mstoykov
mstoykov force-pushed the v2 branch 2 times, most recently from ee2fdf6 to 99aa31a Compare March 31, 2026 21:14
Base automatically changed from v2 to master April 1, 2026 07:34
@mstoykov
mstoykov dismissed szkiba’s stale review April 1, 2026 07:34

The base branch was changed.

@joanlopez
joanlopez temporarily deployed to azure-trusted-signing April 2, 2026 13:17 — with GitHub Actions Inactive
@joanlopez
joanlopez temporarily deployed to azure-trusted-signing April 2, 2026 13:19 — with GitHub Actions Inactive
@joanlopez joanlopez modified the milestones: v2.0.0-rc1, v2.0.0 Apr 8, 2026
@joanlopez
joanlopez merged commit 739c54e into master Apr 9, 2026
52 checks passed
@joanlopez
joanlopez deleted the v2-drop-otel-exportertype branch April 9, 2026 08:25
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 documentation-needed A PR which will need a separate PR for documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants