Bump Scala dependencies to solve vulnerabilities #472
Merged
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
jonathonherbert
approved these changes
Jun 26, 2024
rhystmills
changed the title
|
(Tested Rule Manager and Checker on CODE, also logs - all working well) |
prout-bot
added
Pending-on-Checker
Pending-on-Rule Manager
Seen-on-Rule Manager
and removed
Pending-on-Rule Manager
labels
|
Seen on Rule Manager (merged by @rhystmills 12 minutes and 38 seconds ago) Please check your changes! |
|
Overdue on Checker (merged by @rhystmills 15 minutes and 3 seconds ago) What's gone wrong? |
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.
What does this change?
This bumps some Scala package versions in Typerighter to resolve some high priority vulnerabilities. According to Snyk, this drops the number of high priority backend vulnerabilities from 7 to 1.
Snyk runs for commits in this PR, from newest to oldest:
The remaining vulnerability seems to be unsolved in the latest version of Play.
How to test