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

Submit sbt dependencies to GitHub for vulnerability monitoring #112

Merged
merged 3 commits into from
Jan 13, 2025

Conversation

gu-dependency-graph-integrator[bot]
Copy link
Contributor

@gu-dependency-graph-integrator gu-dependency-graph-integrator bot commented Nov 20, 2024

What does this change?

This PR sends your sbt dependencies to GitHub for vulnerability monitoring via Dependabot. The submitted dependencies will appear in the Dependency Graph on merge to main (it might take a few minutes to update).

What do I need to do?

  • Ensure that the version of sbt in the project is v1.5 or above in order for the dependency submission action to run.
  • A run of this action (Update Dependency Graph for sbt) should have been triggered (see the checks below) when the branch sbt-dependency-graph-87377622a9838adc was created. Sense check the output of the step "Log snapshot for user validation", and make sure that your dependencies look okay.
  • When you are happy the action works, remove the branch name trigger sbt-dependency-graph-87377622a9838adc from the file sbt-dependency-graph.yaml (aka delete line 6), approve this PR, and merge.

Why?

If a repository is in production, we need to track its third party dependencies for vulnerabilities. Historically, we have done this using Snyk, but we are now moving to GitHub’s native Dependabot. Scala is not a language that Dependabot supports out of the box, this workflow is required to make it happen. As a result, we have raised this PR on your behalf to add it to the Dependency Graph.

How has it been verified?

We have tested this workflow, and the process of raising a PR on DevX repos, and have verified that it works. However, we have included some instructions above to help you verify that it works for you. Please do not hesitate to contact DevX Security if you have any questions or concerns.

Further information for sbt

See the sbt workflow documentation for further information and configuration options.

@gu-dependency-graph-integrator gu-dependency-graph-integrator bot requested a review from a team as a code owner November 20, 2024 09:31
@gu-dependency-graph-integrator gu-dependency-graph-integrator bot requested a review from a team November 20, 2024 09:31
Following the PR checklist, now that I’ve confirmed the output of this
workflow looks good I’m removing the test branch trigger.
Now that we’re sending our dependencies to github, we don’t need to send
them to snyk anymore.
Copy link
Contributor

@emdash-ie emdash-ie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've followed the PR checklist and I'm happy to merge (pending CI passing)

@emdash-ie
Copy link
Contributor

@guardian/ophan Would you mind approving this PR? I can't bypass the requirement for code owner approval. (In which case, possibly you should review altogether rather than just approve? 😅 )

@emdash-ie emdash-ie merged commit 88601cd into main Jan 13, 2025
4 checks passed
@emdash-ie emdash-ie deleted the sbt-dependency-graph-87377622a9838adc branch January 13, 2025 10:10
@prout-bot
Copy link

Seen on status.ophan.co.uk (created by @gu-dependency-graph-integrator[bot] and merged by @emdash-ie 5 minutes and 19 seconds ago) Please check your changes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants