Skip to content

ci: auto-label expected OTel api diffs#2255

Closed
zeitlinger wants to merge 1 commit into
mainfrom
ci/auto-label-otel-api-diff
Closed

ci: auto-label expected OTel api diffs#2255
zeitlinger wants to merge 1 commit into
mainfrom
ci/auto-label-otel-api-diff

Conversation

@zeitlinger

Copy link
Copy Markdown
Member

Summary

  • extend the OTel api-diff regeneration workflow to detect the expected shaded OTel incompatibility from generated japicmp reports
  • upload a marker artifact only when the incompatible changes are limited to the expected shaded constructor removal
  • add breaking-api-change-accepted to the open Renovate PR for renovate/otel.instrumentation.version after the workflow pushes regenerated apidiffs

Why

The current workflow only regenerates docs/apidiffs. When an OTel bump changes the shaded package version, the PR can still fail the separate incompatible API gate until the acceptance label is added manually.

Validation

  • mise run lint:fix
  • actionlint .github/workflows/regenerate-api-diff-otel.yml

Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
@zeitlinger

Copy link
Copy Markdown
Member Author

close in favor of #2257

@zeitlinger zeitlinger closed this Jul 1, 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