Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add separate dependency-submission workflow for GitHub actions #3668

Merged
merged 1 commit into from
Apr 16, 2024

Commits on Jan 30, 2024

  1. Add separate dependency-submission workflow

    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.
    bigdaz committed Jan 30, 2024
    Configuration menu
    Copy the full SHA
    de64d8e View commit details
    Browse the repository at this point in the history