chore: group @opentelemetry/* Dependabot updates - #634
Merged
Conversation
The OpenTelemetry JS packages ship from a shared monorepo and move in lockstep, so ungrouped they arrive as a burst of near-identical PRs for a single upstream release. 0.219.0 -> 0.220.0 took three (#601, #605, #606); 0.218.0 -> 0.219.0 took another three (#563, #585, #589); and 2.8.0 -> 2.9.0 took two (#620, #624). 19 @opentelemetry/* PRs merged in the last 90 days. Group them so one upstream release produces one PR. The seven dependencies span three independent version lines — 0.x for the exporters and sdk-node, 2.x for sdk-metrics and resources, 1.x for api and semantic-conventions. A wave that moves only one line just yields a smaller grouped PR, so grouping across them costs nothing. `@opentelemetry/*` covers all seven, and no other group's patterns match them, so nothing is reassigned. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a Dependabot grouping rule so all @opentelemetry/* dependency updates are consolidated into a single PR per upstream OpenTelemetry JS release wave, reducing review/CI churn while keeping existing ignore/group behavior intact.
Changes:
- Introduces a new Dependabot
groups.opentelemetryrule matching@opentelemetry/*. - Documents the rationale for grouping (lockstep releases across the OpenTelemetry JS monorepo) directly in
dependabot.yml.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Why
The OpenTelemetry JS packages ship from a shared monorepo and move in lockstep, so ungrouped they arrive as a burst of near-identical PRs for a single upstream release:
0.219.0→0.220.00.218.0→0.219.02.8.0→2.9.02.7.1→2.8.019
@opentelemetry/*PRs merged in the last 90 days, plus #632 currently open. Each one is its own CI run and its own review.Change
One upstream release wave should now produce one PR.
Version lines
The seven dependencies span three independent version lines:
0.xexporter-metrics-otlp-proto,exporter-trace-otlp-proto,sdk-node2.xresources,sdk-metrics1.xapi,semantic-conventionsGrouping across them costs nothing — a wave that only moves one line simply yields a smaller grouped PR. It does not force unrelated lines to move together.
Verification
react,aisdk,devdependencies,radixui)typescriptmajor-versionignorefrom chore: stop Dependabot proposing TypeScript major bumps #629 is preserved@opentelemetry/*covers all seven dependencies in the workspace@opentelemetry/*, so nothing is reassigned🤖 Generated with Claude Code