ci: one dependabot PR per component for all update types#3467
Merged
Conversation
Per-directory major/range updates multiply review load and, for the Python projects, are broken by construction: the three directories share apache-iggy via a path dependency, so each uv.lock embeds the SDK's requirement metadata, and a per-directory update ships the sibling lockfile rewrite without the manifest change it was derived from - it can never pass the lockfile check (#3451, #3450). Collapse every entry's grouping to a single all-update-types group so each component (SDK impl plus its bdd/examples directories) opens at most one version-update PR per cycle, keeping manifest and lockfile edits for the same dependency in one coherent PR. Security updates bypass groups and stay separate. Also ignore Python base images in the docker entry: the interpreter version is pinned and synced by sync-python-interpreter-version.sh, so a lone image bump would fail the sync check.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3467 +/- ##
============================================
- Coverage 74.61% 74.59% -0.02%
Complexity 937 937
============================================
Files 1248 1248
Lines 123576 123576
Branches 99839 99868 +29
============================================
- Hits 92206 92183 -23
+ Misses 28386 28374 -12
- Partials 2984 3019 +35
🚀 New features to boost your workflow:
|
spetz
approved these changes
Jun 13, 2026
numinnex
approved these changes
Jun 15, 2026
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
3 participants
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.
Per-directory major/range updates multiply review load and, for
the Python projects, are broken by construction: the three
directories share apache-iggy via a path dependency, so each
uv.lock embeds the SDK's requirement metadata, and a per-directory
update ships the sibling lockfile rewrite without the manifest
change it was derived from - it can never pass the lockfile check
(#3451, #3450). Collapse every entry's grouping to a single
all-update-types group so each component (SDK impl plus its
bdd/examples directories) opens at most one version-update PR per
cycle, keeping manifest and lockfile edits for the same dependency
in one coherent PR. Security updates bypass groups and stay
separate.
Also ignore Python base images in the docker entry: the
interpreter version is pinned and synced by
sync-python-interpreter-version.sh, so a lone image bump would
fail the sync check.