Repository navigation
Run the Gradle dependency submission when a dependency file changes - #105
Merged
Merged
Conversation
The weekly run left the graph up to a week old after a dependency update. GitHub checks new advisories against the last submitted graph, so a run is needed only when the dependencies change. Assisted-by: Claude:claude-opus-5-5
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.
Why
The weekly run left the dependency graph up to a week old after a dependency update, unless someone started the workflow by hand. GitHub checks new advisories against the last submitted graph, so a run is needed only when the dependencies change.
What changed
With the new triggers, the dependency submission workflow runs on a push to
mainthat changes a file which can change the resolved dependencies or the Gradle version, and on a manual run. The weekly cron is removed.Review notes
gradle.properties, the version catalog and the Gradle wrapper. It also covers other version catalogs, dependency lock files andbuildSrc, for later. A version that changes in a file outside the list does not start a run.dependency-submission-with-gradle@v4can change the excluded configurations or the scopes without a change in this repository. The comment says to start the workflow by hand then.Test scope
pushandworkflow_dispatch.main, on the next change of a listed file.Risk: needs a human review, assessed at 10d7dc1
risk:low.