Skip to content

chore(deps): bump OpenTelemetry API to 1.67.0 (CI reproduction of #866) - #867

Closed
zhongkechen wants to merge 1 commit into
mainfrom
ci/otel-api-1.67.0-pr866
Closed

zhongkechen wants to merge 1 commit into
mainfrom
ci/otel-api-1.67.0-pr866

Conversation

@zhongkechen

Copy link
Copy Markdown
Contributor

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Issue Link, if available

CI reproduction of #866.

Description

Updates otel.api.version from 1.66.0 to 1.67.0 in otel-plugin/src/test/compatibility/b1/pom.xml. This draft reproduces the exact one-line patch from #866 on current main so we can observe CI results.

Demo/Screenshots

Not applicable; dependency fixture only.

Design

  • Design note: not needed; no feature, option, or public API change.
  • Simpler options: not applicable; no logic added.
  • Root cause: not applicable; dependency update, not a bug fix.
  • Net source lines: zero (+1/-1 in the POM); public API members: zero.

Assumptions

OpenTelemetry 1.67.0 compatibility remains unverified. The existing .github/scripts/verify_otel_api_compatibility.py explicitly supplies -Dotel.api.version for 1.49.0 and 1.66.0, so that CI matrix overrides the updated POM default and does not exercise 1.67.0.

Decisions not covered by the issue or the design note

Checklist

  • I have filled out every section of the PR template
  • I have thoroughly tested this change (CI pending)
  • Every new branch has a test that fails without it (not applicable; no new logic)
  • For a bug fix: regression test evidence (not applicable)
  • Every edited test expectation is listed (none changed)

Testing

Unit Tests

No new tests; this only updates the existing compatibility fixture. Existing tests will run in CI.

Integration Tests

No new tests; existing CI checks will provide results, subject to the version override described above.

Examples

Not applicable.

@zhongkechen zhongkechen closed this Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant