Exclude OpenTelemetry updates from the grouped weekly Renovate PR - #8727
Closed
trask wants to merge 1 commit into
Closed
Exclude OpenTelemetry updates from the grouped weekly Renovate PR#8727trask wants to merge 1 commit into
trask wants to merge 1 commit into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR updates Renovate grouping configuration so OpenTelemetry-related dependency updates don’t get bundled into the weekly “all patch and minor versions” group PR, allowing dogfooding and cascaded releases to land promptly.
Changes:
- Clarifies the weekly grouping rule comment to reflect that it applies to both patch and minor updates.
- Adds exclusions intended to keep OpenTelemetry Maven artifacts and GitHub-sourced OpenTelemetry dependencies out of the weekly grouped PR.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+27
to
+30
| matchPackageNames: [ | ||
| '!io.opentelemetry**', | ||
| '!open-telemetry/**', | ||
| ], |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8727 +/- ##
=========================================
Coverage 91.26% 91.27%
- Complexity 10461 10462 +1
=========================================
Files 1006 1006
Lines 28244 28244
Branches 3564 3564
=========================================
+ Hits 25778 25779 +1
Misses 1674 1674
+ Partials 792 791 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Member
Author
|
Reopened from a fork branch as #8728, which has the same commit and the same diff. Closing this one. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
OpenTelemetry dependency updates now always get their own Renovate PR instead of being swallowed into the grouped weekly
all patch and minor versionsPR. These updates are used for dogfooding and for cascaded releases across the OpenTelemetry Java repos, so batching them until Tuesday delays the release chain.The affected artifacts are
io.opentelemetry.contrib:opentelemetry-aws-xray-propagator,io.opentelemetry.proto:opentelemetry-proto, andio.opentelemetry.semconv:opentelemetry-semconv-incubating.The exclusion is written as
!io.opentelemetry**without a colon, so it covers every OpenTelemetry group id rather than only the bareio.opentelemetrygroup.!open-telemetry/**covers dependencies sourced from GitHub.OpenTelemetry-published Docker images such as
otel/opentelemetry-collector-contribare deliberately still grouped, because they are test infrastructure rather than part of a cascaded release.GitHub Actions and Dockerfile updates are unaffected. The later
weekly updaterule matches by manager and still overrides the grouping for them, includingopen-telemetry/shared-workflowsaction bumps.The comment on the rule also said "group all patch updates" even though the rule has covered minor updates too; that is corrected here.