Use capybara-webmock fork to be able to update Rack - #12009
Merged
Conversation
changelog: Internal, Maintenance, Use capybara-webmock fork to be able to update Rack
Sgtpluck
approved these changes
Mar 21, 2025
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
2 participants
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.
🛠 Summary of changes
There is an outstanding rack vulnerability (#11954) that we have been blocked on addressing due to an issue with the
capybara-webmockdependency. There is an open pull request to address the issue, but it has not been merged or released. I have created a fork 18F/capybara-webmock that incorporates the changes in hashrocket/capybara-webmock#56.This PR updates so that we use the new fork and updates Rack to address the outstanding vulnerabilities.