Repository navigation
chore(ci): group dependabot updates and pin actions to SHAs - #196
Merged
Merged
Conversation
peterj
approved these changes
Aug 27, 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
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.
Dependabot opened 7 PRs on its first run with warnings. This PR fixes 2 things:
The version update groups had
update-types: [minor, patch]on them, which does not mean "handle majors elsewhere", it means majors fall out of the group and each gets its own PR. That accounts for 3 of the 7. Dropped those filters, merged uv 3 groups into 2 and npm 2 into 1, and narrowed the npm major ignore from"*"(which silenced everything in ui/, not just react/vite/antd) to the 4 packages that actually need a migration. Should be 2 or 3 grouped PRs a week now instead of 7 to 10.All 10 actions were on mutable tags. Pinned every one to a commit SHA with the version in a trailing comment, same as we do elsewhere. Tags can be repointed, and in release.yml that reaches PYPI_TOKEN, GHCR packages:write, and contents:write. Dependabot bumps SHA pins and rewrites the comment automatically, so no extra upkeep.
Also fixes setup-uv being on v6 in publish-evaluator-sdk.yml while everything else was on v7.
Base images in the Dockerfile stay on tags on purpose. We want rolling OS security patches there; the SHA pinning is about not executing code from a mutable ref.
Closes #189, #190, #191, #192, #193, #194, #195