Implement a merge freeze when an "[chore] Update core dependencies" PR on opentelemetry-collector-contrib is present #12837
+10
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Extend the merge freeze logic in
.github/workflows/scripts/check-merge-freeze.sh
to include open PRs titled "[chore] Update core dependencies" in theopentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib
repository, in addition to the existing check for "[chore] Prepare release" PRs in the core repo.This ensures that no PRs can be merged into
main
while a core update PR is pending in contrib, helping us avoid version drift and keep dependencies aligned between core and contrib.Link to tracking issue
Fixes #12830
Testing
Tested locally by:
opentelemetry-collector-contrib
check-merge-freeze.sh
script to confirm it correctly blocks mergesDocumentation
No user-facing documentation changes needed. This change only affects internal CI logic.