Update sidekiq: 6.0.0 → 6.0.4 (patch) #180
Closed
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.0.0 → 6.0.4) · Repo · Changelog
Release Notes
6.0.4 (from changelog)
6.0.3 (from changelog)
6.0.2 (from changelog)
6.0.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 more commits than we can show here.
Release Notes
2.0.8 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
Bumping versionIntroduce a new base class to avoid breaking when upgradingAdd a version prefix to the private id to make easier to migrate old valuesFallback to the public id when reading the session in the pool adapterAlso drop the session with the public id when destroying sessionsFallback to the legacy id when the new id is not foundAdd the private idrevert conditionals to masterremove NullSessionremove || raise and get closer to masterstore hashed id, send public iduse session id objectsremove more nilstry to ensure we always have some kind of objectRelease Notes
4.1.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 14 commits:
Release 4.1.3Merge pull request #874 from darshanime/handle_node_failureRescue connection errors for call_loop, call_pipelineDecrease retries for redis node failures in specsAdd note in readmeHandle permanent node failures for redis clusterMerge pull request #872 from fatkodima/bzpop-useless-hashDo not allocate useless hash for b*pop* commandsMerge pull request #871 from mfly/allow-to-skip-ssl-host-checkAllow to skip SSL host check with verify_hostname: falseMerge pull request #868 from pgeraghty/tcp_nodelaySet TCP_NODELAY to avoid unnecessary delays during MULTIMerge pull request #862 from ioquatix/patch-1Add "See Also" section to README.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