chore: update ghcr.io/dragonflydb/dragonfly (v2.0.0 → v2.0.2) #36
Loading…
Reference in a new issue
No description provided.
Delete branch "updatarr/ghcr.io-dragonflydb-dragonfly-ec4d682d68"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Updates
ghcr.io/dragonflydb/dragonfly.Links:
Automerge: Enabled
Updates
ghcr.io/dragonflydb/dragonflyv2.0.0v2.0.2[2] L108
Files
.forgejo/workflows/ci.yml.forgejo/workflows/release.yamlRelease notes
ghcr.io/dragonflydb/dragonfly (v2.0.0 → v2.0.2)
v2.0.2: v2.0.2Compare source
Source
This is a patch release.
What's Changed
DFLYMIGRATEwas sent to a server that is not in cluster mode. It now returns the standard "Cluster is disabled" error (#8290).*wildcards inKEYS,SCAN/HSCAN/SSCAN/ZSCAN MATCH, ACL key patterns,PSUBSCRIBEandCONFIG GET. Matching is now iterative, so it no longer overflows the fiber stack, and it is also faster (#8350).COPYorLMOVE). Source keys are now checked for read access and destination keys for write access (#8249).INFO persistencereportingrdb_bgsave_in_progress:1forever after aBGSAVE.rdb_last_bgsave_statusis now also updated when a background save finishes (#8459).CLUSTER NODES/SLOTS/SHARDS, instead of the address passed toREPLICAOF(#8241).maxmemorybucket. No keys, data, hostnames or addresses are sent. (#8469).Full Changelog: v2.0.0...v2.0.2