chore: schedule weekly composer and actions dependency updates - #13
Merged
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
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.
There was no
.github/dependabot.yml, so only security updates ran — nothing bumped dependencies routinely, which iswhy PR #8 had to move the workflow actions off the deprecated Node 20 runtime by hand.
Adds two weekly updaters (Monday, Europe/Berlin):
symfony/*grouped into one PR, since the components release in lockstep.composer.jsonpins7.4.*, so this only ever offers patch releases inside the LTS branch; moving to 8.x stays a deliberate manualchange.
start; the value shows up at the next runner-runtime deprecation.
Both use
commit-message.prefix: choreto match the repo'schore:/fix:/feature:convention rather thanDependabot's default
build(deps).Verify
The YAML parses and the keys are well-formed, but GitHub only validates a Dependabot config once it is on the default
branch — there is no local or API validator. The real check is Insights → Dependency graph → Dependabot after merge:
both ecosystems should be listed with no config error.