chore(deps): group dependent bot PRs - #576
Closed
joshdimanteto wants to merge 1 commit into
Closed
Conversation
joshdimanteto
force-pushed
the
group-dependabot-prs
branch
from
June 25, 2026 14:30
ac9e75f to
2f80d02
Compare
Contributor
Author
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
1 participant
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.
Description
Configure Dependabot to manage Docker, GitHub Actions, and uv dependencies across the develop and main branches. Updates are scheduled regularly with a 7-day cooldown. GitHub Actions and uv dependencies are grouped into single PRs to simplify review and maintenance.
Quoted from IMS repo
We use Renovates default of 3 days for npm packages on the frontend, here it seems for pip 7 days is generally considered preferable, so went for that. Doesnt resolve supply chain attacks, but relies on the community to notice something is wrong which typically occurs within a short timespace after packages are released.
Testing Instructions
icatdb Generator Script Consistency TestCI job fails, is this because of a deliberate change made to the script to change generated data (which isn't actually a problem) or is here an underlying issue with the changes made?fix:,feat:orBREAKING CHANGE:so a release is automatically made via GitHub Actions upon merge?