Add workflow to periodically check for dependency updates #21
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.
This adds a workflow to run
./gradlew versionCatalogUpdate
and, if the catalog is updated, create a PR with the diffs. The workflow is scheduled to run once a week, and can be triggered manually too.The heavy lifting is in the
peter-evans/create-pull-request
action that will manage creating and updating the PR when changes are detected. Because during the buildgradlew
is also changed, that change is reverted before creating the PR.The PR does not give a comprehensive description of the changed dependencies, it merely produces a new branch and a diff. The created branch can be used to verify the dependency updates or do adjustments before merging, mainly serving as a reminder that updates are available.
The initial run will update the formatting of the catalog so that will be a bit noisy :)