Update dependency predis/predis to v1.1.10#16
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
9ba4959 to
6aadbda
Compare
Author
|
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.
This PR contains the following updates:
1.1.1→1.1.10Release Notes
predis/predis (predis/predis)
v1.1.10: Predis v1.1.10Compare Source
Session/HandlerConnection/Aggregate/SentinelReplicationv1.1.9: Predis v1.1.9Compare Source
StreamConnectionv1.1.8: Predis v1.1.8Compare Source
v1.1.7: Predis v1.1.7Compare Source
spurious responses returned after reconnecting to Redis because the underlying
reader was not properly reset by discarding buffered replies after disconnecting
(ISSUE #363).
cweagans/composer-patchesdev dependency and apply patchesusing
post-update-cmdscript.v1.1.6: Predis v1.1.6Compare Source
That was fast, but we had a bug in v1.1.5 so we needed to release a fix ASAP.
FIX: reverted support for sentinels authentication implemented in v1.1.5 as it was bugged (see ISSUE #658), sorry for the trouble. This is now postponed as it requires a more thorough investigation.
v1.1.5: Predis v1.1.5Compare Source
Here we have a new patch release!
NOTE: We are still missing handlers for commands added in Redis 4, 5 and 6. We will get on par eventually, in the meanwhile you can define your own ones or use
Predis\Client::executeRaw(). Read this post for details about how to properly implement support for new commands if you would like to add missing ones and share your work with us by creating pull requests, contributions are always greatly appreciated!NOTE intentionally commented out, please read the release notes for v1.1.6
FIX: authentication for sentinels is now supported, previously it was not possible to specify apasswordfor sentinels as its value was stripped during initialization because sentinels did not support authentication until Redis 5. Please note that with the current implementation each sentinel must have its ownpasswordparameter set in the parameters list despite this password is the same for all sentinels (read howrequirepassworks on the Redis docs). In this case you should avoid using the globalparametersclient option used to set default parameters for every connection created by Predis as this would end up using the same password even when connecting to actual Redis nodes. We are investiganting how to make it easier to specify the required password to access sentinels only once instead of repeating it for each sentinel.FIX: the username is now correctly retrieved from the userinfo fragment of the URI when using the
redisscheme and ausername:passwordpair is present. Values retrieved from the userinfo fragment always override the ones specified inusernameandpasswordif those fields are present in the query string.FIX:
Predis\Connection\WebdisConnectionwas unable to connect to Webdis when using an IPv4 address in the URL and this is probably due to some change in cURL internals since the last time we tested it.FIX: an exception is thrown when passing
FALSEor any value evaluating toFALSEto thereplicationclient option. This was supposed to be unsupported, in fact it actually breaks client initialization and raises a PHP warning. Now the user is alerted with anInvalidArgumentExceptionand a proper message. (PR #381).v1.1.4: Predis v1.1.4Compare Source
Here is a new patch release for
v1.1with more improvements and fixes.NOTE: We are still missing handlers for commands added in Redis 4, 5 and 6. We will get on par eventually, in the meanwhile you can define your own ones or use
Predis\Client::executeRaw(). Read this post for details about how to properly implement support for new commands if you would like to add missing ones and share your work with us by creating pull requests, contributions are always greatly appreciated!The client can now handle ACL authentication when connecting to Redis 6, just pass both
usernameandpasswordto connection parameters and Predis switches to using the augmented variant ofAUTH:As usual Redis servers protected only by a password can still be accessed with just the
passwordparameter. See the Redis documentation for more details about Redis ACLs.FIX:
NULLor zero-length string values inpasswordanddatabasedo not trigger spuriousAUTHandSELECTcommands anymore when connecting to Redis.This fix addresses some old issues with certain libraries and frameworks (see ISSUE #436).
Empty connection parameters do not make much sense anyway so, in the next major release, any field containing
NULLor a zero-length string will be stripped away when converting URI strings and named arrays to instances ofPredis\Connection\Parameters.FIX:
SORTnow always triggers a switch to the master node in replication configurations instead of just when theSTOREmodifier is specified. The reason for this change is thatSORTis always considered to be a write operation and it actually fails with a-READONLYerror response when executed against a replica node (ISSUE #554).FIX: using
foreach()on a client instance when it is connected to a single Redis server does not throw an exception anymore but the iteration will run for just one loop returning a new client for the underlying single-node connection (ISSUE #552, PR #556).Using
foreach()actually makes sense when using aggregate connection backends for client-side sharding orredis-clusterbut there is no reason (and it is wrong anyway) to throw an exception inPredis\Client::getIterator()when the client is connected to a single server.FIX:
Predis\Cluster\Distributor\HashRing::addNodeToRing()was calculating the hash required for distribution by usingcrc32()directly instead of the methodPredis\Cluster\Hash\HashGeneratorInterface::hash()implemented by the class itself. This fix does not have any impact on existing cluster deployments using client-side sharding based on this distributor simply because it does not take any external hash generators so distribution is not going to be affected.Improved
@methodannotations for methods responding to Redis commands defined byPredis\ClientInterfaceandPredis\ClientContextInterface(PR #456 and PR #497, other fixes applied after further analysys).v1.1.3: Predis v1.1.3Compare Source
github.com/nrk/predistogithub.com/predis/predis.cweagans/composer-patchesdependency torequire-dev..patchfiles in exports.v1.1.2: Predis v1.1.2Compare Source
Predis is under new management. Read the announcement and checkout the roadmap 🚀
If you (or your business) would like to support the development of this fantastic library and ensure it's bright future, please use the GitHub Sponsor button 🙏🏻
Changes
the input value passed to the
hash()method is an integer (PR #450).ZSCANandHSCANworking withPHP 7.2 due to a breaking change, namely the removal of
each()(PR #448).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.