Upgrade nokogiri package (low severity vulnerability) #3829
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
Ponnia-M
requested review from
PaulKBaumann,
jahenkor-navapbc,
gabezurita and
brostk
and removed request for
PaulKBaumann and
jahenkor-navapbc
|
Note: seems we have a flaky test in lint-and-test! We may want to comment it out since we're shutting down the service. |
JaCoCo Test Coverage
|
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 was the problem?
Secrel failed this morning due to this low severity vulnerability (nokogiri package).
How does this fix it?[^1]
An upgrade to nokogiri version 1.16.8 should prevent Secrel from failing related to this low severity vulnerability. For additional context, running
bundle update nokogiriupgrades Nokogiri and its dependencies as well as other gems due to shared dependencies.