Fix Ruby dependency vulnerabilities - #4
Merged
Conversation
This file contains hidden or 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
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 changed
Why
The
github-pagesumbrella gem allows vulnerable transitive versions to remain locked even though patched releases satisfy its dependency constraints. Updating only the affected transitive dependencies removes the vulnerabilities without changing the site framework or deployment model.Impact
No site behavior is intentionally changed. The Jekyll site continues to build with the GitHub Pages dependency set, while the vulnerable Ruby dependencies are replaced with compatible patched releases.
Validation
bundle exec ruby test/site_test.rb— 11 runs, 115 assertions, 0 failuresbundle-audit check --update— No vulnerabilities foundgit diff --check— clean