chore(ci): group Dependabot updates into single weekly PRs - #35
Merged
Conversation
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
2 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.
Summary
groupsto bothgithub-actionsandcomposerDependabot entries so all updates in each ecosystem are batched into a single weekly PR instead of one per package.versioning-strategy: lockfile-onlyto the Composer entry so Dependabot updates onlycomposer.lock, never the constraint ranges incomposer.json.Why
Dependabot was opening one PR per package (#18, #28, #29, #33, #34), causing them to race against each other and against manual lock-refresh PRs like #30.
All Composer deps are dev-only, so there's no value in tracking them individually.
Effect
deps(...)PR for all Composer dev deps and one groupedci(...)PR for all GitHub Actions updates.composer.lockrefresh PRs.