🚨 [security] Update all of rails: 5.2.4.3 → 5.2.4.4 (patch)#316
Closed
depfu[bot] wants to merge 1 commit intodevelopfrom
Closed
🚨 [security] Update all of rails: 5.2.4.3 → 5.2.4.4 (patch)#316depfu[bot] wants to merge 1 commit intodevelopfrom
depfu[bot] wants to merge 1 commit intodevelopfrom
Conversation
Contributor
Author
|
Closed in favor of #337. |
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.
🚨 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 (5.2.4.3 → 5.2.4.4) · Repo
Commits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperCommits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperCommits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperCommits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperSecurity Advisories 🚨
🚨 Potential XSS vulnerability in Action View
Commits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperCommits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperCommits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperCommits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperCommits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperCommits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperRelease Notes
2.7.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 9 commits:
version bump to v2.7.0Merge pull request #190 from ahorek/page_breakupdate CHANGELOGadd page-break to safelistMerge pull request #192 from b7kich/maintain_shorthand_css_important_ruleupdate CHANGELOGprefer Array#<< to creating a new arrayscrub_css should not drop `!important` from shorthand css propsupdate json dev dependencyRelease Notes
5.14.2 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 4 commits:
prepped for release- Bumped ruby version to include 3.0 (trunk).whitespaceI am an idiot... fixed a last-day-of-month testing bug. I don't think I've done that in 15+ years. :PRelease Notes
2.5.3 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 37 commits:
Bump version.Remove ancient appveyor config.Prepare CHANGES.md for next release.fix for #241Fix Actions CI for macOSssl_socket_spec.rb - move require inside blockFixes for use when OpenSSL is not loadedFix warning: Use `result.unpack1("i")` instead of `result.unpack("i").first`. (convention:Style/UnpackFirst)Setting 'Enabled: false' for the new cops of RubocopFix warning: Metrics/LineLength has the wrong namespace - should be LayoutUpdate rubocop version to 2.4Fix warning: The `Lint/HandleExceptions` cop has been renamed to `Lint/SuppressedException`.Fix warning: The `Layout/AlignHash` cop has been renamed to `Layout/HashAlignment`Bumb Rubocop to 0.82.0Use truffleruby-head in CICI: Exclude TruffleRuby on WindowsRemove travis config and update github actions.Update travis configuration.Add ruby 2.7Merge pull request #234 from MSP-Greg/add-actionsRemove redundant jobs from AppVeyorRemove redundant jobs from TravisAdd Actions CI - workflow.ymlextconf.rb - add devkit for mingwFix Warning: unrecognized cop Performance/RegexpMatch found in .rubocop.ymlFix Lint/UnneededCopEnableDirectiveFix Naming/RescuedExceptionsVariableNameFix Lint/UnneededCopEnableDirectivedisable Layout/AlignHashFix Style/ExpandPathArgumentsFix Layout/EmptyLineAfterGuardClauseFix Style/ExpandPathArgumentsbump rubocop to 0.74.0CI: Add 2.7 to the matrixPolish examples/echo_server.rbUpdate CHANGES.mdUpdate CHANGES.mdCommits
See the full diff on Github. The new version differs by 2 commits:
v5.2.4.4Fix XSS vulnerability in `translate` helperRelease Notes
0.7.3 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
Bump version to 0.7.3Accept HTTP responses that have an empty reason-phrase, per RFC 2616Depfu 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