Repository navigation
Add a weekly Gradle dependency submission workflow - #104
Merged
Merged
Conversation
Assisted-by: Claude:claude-opus-5-5
Assisted-by: Claude:claude-opus-5-5
mmalfertheiner
approved these changes
Nov 12, 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.
Goal
GitHub does not read Gradle build files, so postgresql-operator gets no Dependabot alerts for its Java dependencies. Today its dependency graph has only the GitHub Actions of its workflows.
What changed
A new workflow submits the resolved Gradle dependency graph to GitHub every Monday and on a manual run. It uses
dependency-submission-with-gradle@v4withjava-version: 25andproject-type: quarkus(aboutbits/github-actions-java#12).Review notes
Test scope
quarkus-operator-sdk-helmis "runtime".main.Risk: needs a human review, assessed at 6a44203