🚨 [security] Update rails 7.0.5 → 7.0.5.1 (minor) #1289
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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rails (7.0.5 → 7.0.5.1) · Repo
Commits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toSecurity Advisories 🚨
🚨 Possible XSS via User Supplied Values to redirect_to
Commits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toRelease Notes
5.18.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 7 commits:
prepped for releaseRemoved 2.6 from CI.- Avoid extra string allocations when filtering tests. (tenderlove)- Only mention deprecated ENV['N'] if it is an integer string.- Push up test_order to Minitest::Runnable to fix minitest/hell. (koic)Use minitest organization in links (hsbt)updated dates / versions in rails faqCommits
See the full diff on Github. The new version differs by 3 commits:
Preparing for 7.0.5.1 releaseupdate changelogAdded check for illegal HTTP header value in redirect_toRelease Notes
0.4.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 7 commits:
Bump up v0.4.0Raise exception instead of throw/catch for timeouts (#30)Move gemspec files to top of lib directory.Merge pull request #31 from nobu/test-unit-ruby-coreUse released version of test-unit-ruby-coreMerge pull request #29 from ruby/update-test-lib-20230324Update test libraries from https://github.com/ruby/ruby/commit/b4e438d8aabaf4bba2b27f374c787543fae07c58Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands