[ruby] Update sidekiq 6.5.8 → 6.5.12 (patch) #92
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.
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?
✳️ sidekiq (6.5.8 → 6.5.12) · Repo · Changelog
Release Notes
6.5.9 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 8 commits:
bump
Use broadcast_to, fixes #6070
changes, bump
Remove old initializer, fixes #6067
Cherry pick:
Merge 62c90d7
bump, prep
formatting, ensure environment is updated in Sidekiq.options
✳️ redis (4.8.0 → 4.8.1) · Repo · Changelog
Release Notes
4.8.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 6 commits:
Release 4.8.1
Automatically reconnect after fork regardless of `reconnect_attempts`
Merge pull request #1146 from bpo/fix-sadd-returns-boolean-changelog
fix changelog instructions for enabling 5.0 behavior
Merge pull request #1137 from tgxworld/fix_deprecation_note
Fix deprecation note for srem
Release Notes
2.4.1 (from changelog)
2.4.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 8 commits:
changes, bump
Ability to optionally drop all connections after fork (#177)
Set "changelog_uri" in gemspec to point to Changes.md (#176)
Opt-in for MFA requirement (#171)
release
Add Ruby 3.2 to the CI matrix. (#169)
Automatically drop all connections after fork (#166)
Update readme: non critical -> non-critical (#164)
Release Notes
2.2.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 10 commits:
Bump patch version.
Regenerate SPEC (#2102)
Fix inefficient assert pattern in Rack::Lint (#2101)
Prefer ubuntu-latest for testing. (#2095)
Update cookie.rb (#2092)
adds missing 2.2.7 to CHANGELOG.md (#2081)
Limit file extension length of multipart tempfiles (#2069) (#2075)
Bump patch version.
Support underscore in host names for Rack 2.2 (Fixes #2070) (#2071)
Merge branch '2-2-sec' into 2-2-stable
Depfu 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
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.