Update Rails out of CVE-2022-32224 #2227
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
|
I was upgrading the example app to Rails 7 here, and it turns out that we need some changes to make it work with Rails 7. And that the Appraisal-driven Rails 7 app was actually running Rails 6.1 😓 So I'll fix that first. |
|
Giving up on the Rails 7 update and sticking to 6.1.* for now. Updated description to reflect this. |
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.
Rails 6.1.6 fails the gem audit due to a security advisory. Let's upgrade out of it.
Ideally I should upgrade to Rails 7, but there's something tricky about it. I'm going to stick to 6.1.x for now as the security advisory breaks the build, and therefore it is more important.