Let Dependabot watch the GitHub Actions this workflow uses - #2
Merged
Conversation
An action referenced by a moving tag changes without a commit on our side, so nobody sees it happen. Weekly, grouped, scoped to Actions only: an update now arrives as a pull request that runs CI and gets read before it lands.
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.
An action referenced by a moving tag can change without any commit on our side, so nobody sees it happen. This adds a weekly, grouped Dependabot config scoped to GitHub Actions only, so an update arrives as a pull request that runs CI and gets read before it lands.
Package dependencies are deliberately not watched here - Dependabot's security alerts already cover those, and watching them would open pull requests for advisories in test-only dependencies that never reach a user of the package.
In
junit5-reporterthis file has a second job:gradle/actions/setup-gradleis pinned to a commit so a retagged release cannot reach the runner, and a pinned action otherwise never picks up its own security fixes. The pin and this file are one change, not two.