-
Notifications
You must be signed in to change notification settings - Fork 104
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
Support GitHub dependencies review action/api #879
Comments
Hm, don't know if this is a GitHub issue, but the workaround to run the review action in another job didn't work: reviewDependencies:
runs-on: ubuntu-latest
needs:
- build
if: github.event_name == 'pull_request'
steps:
- uses: actions/dependency-review-action@v3
with:
retry-on-snapshot-warnings: true Update: This feature isn't yet implemented according to the issue tracker: actions/dependency-review-action#545, but the docs already mention it: https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#best-practices-for-using-the-dependency-review-api-and-the-dependency-submission-api-together Alternative: gradle-build-action could call the GitHub review REST api too (or via opt-in). |
Thanks for trying this out. The action was never tested with the dependency-review-action, since it wasn't compatible with Dependency Submission at the time. It looks like #882 will address the underlying issue. I'll leave this open until we can confirm that things are working. |
@hfhbd A fix for this issue has been added to the |
Thanks for checking. I'll release |
@hfhbd You should be able to switch back to |
Currently, the dependency submission is called in the Post step, not directly after the execution of Gradle. This is incompatible with the https://github.com/actions/dependency-review-action, which validates the submitted dependencies (from a PR) and will fail your build, eg if you submit vulnerabilities in the PR. The review action needs to be run after Gradle and after the submission of dependencies.
The text was updated successfully, but these errors were encountered: