Add separate dependency-submission workflow for GitHub actions
#3668
Conversation
This file contains 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
With the introduction of `gradle/actions/dependency-submission`, it is now simpler (and recommended) to use a separate workflow for generation and submission of GitHub Dependency Graph. This workflow attempts to detect and submit all dependencies that would be resolved during build execution, without requiring the execution of any particular task. In basic testing it appears that the generated dependency graph contains the same dependencies as before. A few things to note: The new workflow will submit a dependency graph with a different "correlator" to the previous one. This means that duplicate dependencies (and alerts) may appear until the older graph ages out and is automatically purged. (Period of hours to days). Manually dismissed Dependabot Alerts may need to be re-dismissed after switching to the new workflow.
sbrannen
changed the title
dependency-submission workflow for GitHub actions
|
@bigdaz Why did you close the PR? |
I was just cleaning up open PRs of mine that hadn't got any traction. It's still valid as far as I know. |
marcphilipp
approved these changes
Apr 16, 2024
|
Thanks, Daz! Sorry it took so long to get this merged! |
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.
With the introduction of
gradle/actions/dependency-submission, it is now simpler (and recommended) to use a separate workflow for generation and submission of GitHub Dependency Graph.This workflow attempts to detect and submit all dependencies that would be resolved during build execution, without requiring the execution of any particular task. In basic testing it appears that the generated dependency graph contains the same dependencies as before.
A few things to note:
The new workflow will submit a dependency graph with a different "correlator" to the previous one. This means that duplicate dependencies (and alerts) may appear until the older graph ages out and is automatically purged. (Period of days).
Manually dismissed Dependabot Alerts may need to be re-dismissed after switching to the new workflow.
I hereby agree to the terms of the JUnit Contributor License Agreement.
Definition of Done
@APIannotations