chore: update ghcr.io/dragonflydb/dragonfly (v2.0.0 → v2.0.2) #396

Merged

Wuast94 merged 1 commit from updatarr/ghcr.io-dragonflydb-dragonfly-ec4d682d68 into main 2026-10-08 04:37:54 +02:00

Conversation 0 Commits 1 Files changed 2 +2 -2

Wuast94 commented 2026-10-08 00:41:15 +02:00

Owner

• Copy link
• Copy Markdown

Updates ghcr.io/dragonflydb/dragonfly.

Links:

• Source
• Package
• Release
• Compare

Automerge: Enabled

Updates

Dependency	From	To	Type	Locations
ghcr.io/dragonflydb/dragonfly	v2.0.0	v2.0.2	patch	[1] L31 [2] L108

Files

• [1] .forgejo/workflows/ci.yml
• [2] .forgejo/workflows/release.yaml

Release notes

ghcr.io/dragonflydb/dragonfly (v2.0.0 → v2.0.2)

v2.0.2: v2.0.2

Compare source

Source

This is a patch release.

What's Changed

• Fixed a crash when DFLYMIGRATE was sent to a server that is not in cluster mode. It now returns the standard "Cluster is disabled" error (#8290).
• Fixed a crash on glob patterns with many * wildcards in KEYS, SCAN/HSCAN/SSCAN/ZSCAN MATCH, ACL key patterns, PSUBSCRIBE and CONFIG GET. Matching is now iterative, so it no longer overflows the fiber stack, and it is also faster (#8350).
• Fixed a crash in blocking commands when a watched key holds a value of the wrong type. The registered blocked keys are now cleaned up (#8305).
• Fixed a crash when restoring an HNSW vector index while a key is being deleted concurrently (#8466).
• Fixed ACL permission checks for commands that both read and write keys (such as COPY or LMOVE). Source keys are now checked for read access and destination keys for write access (#8249).
• Fixed INFO persistence reporting rdb_bgsave_in_progress:1 forever after a BGSAVE. rdb_last_bgsave_status is now also updated when a background save finishes (#8459).
• In emulated cluster mode, replicas now advertise the master's announced address in CLUSTER NODES/SLOTS/SHARDS, instead of the address passed to REPLICAOF (#8241).
• The daily version check now also sends anonymous deployment info: architecture, I/O backend, cloud provider, thread count, kernel version, uptime and a maxmemory bucket. No keys, data, hostnames or addresses are sent. (#8469).

Full Changelog: v2.0.0...v2.0.2

Updates [`ghcr.io/dragonflydb/dragonfly`](https://github.com/dragonflydb/dragonfly). Links: - [Source](https://github.com/dragonflydb/dragonfly) - [Package](https://ghcr.io/dragonflydb/dragonfly) - [Release](https://github.com/dragonflydb/dragonfly/releases/tag/v2.0.2) - [Compare](https://github.com/dragonflydb/dragonfly/compare/v2.0.0...v2.0.2) Automerge: Enabled ### Updates | Dependency | From | To | Type | Locations | | --- | --- | --- | --- | --- | | <code>ghcr.io/dragonflydb/dragonfly</code> | <code>v2.0.0</code> | <code>v2.0.2</code> | patch | [1] L31<br>[2] L108 | ### Files - [1] <code>.forgejo/workflows/ci.yml</code> - [2] <code>.forgejo/workflows/release.yaml</code> ### Release notes <details> <summary>ghcr.io/dragonflydb/dragonfly (v2.0.0 → v2.0.2)</summary> ### [`v2.0.2`](https://github.com/dragonflydb/dragonfly/releases/tag/v2.0.2): v2.0.2 [Compare source](https://github.com/dragonflydb/dragonfly/compare/v2.0.0...v2.0.2) [Source](https://github.com/dragonflydb/dragonfly) ## This is a patch release. ### What's Changed - Fixed a crash when `DFLYMIGRATE` was sent to a server that is not in cluster mode. It now returns the standard "Cluster is disabled" error ([#8290](https://github.com/dragonflydb/dragonfly/pull/8290)). - Fixed a crash on glob patterns with many `*` wildcards in `KEYS`, `SCAN`/`HSCAN`/`SSCAN`/`ZSCAN MATCH`, ACL key patterns, `PSUBSCRIBE` and `CONFIG GET`. Matching is now iterative, so it no longer overflows the fiber stack, and it is also faster ([#8350](https://github.com/dragonflydb/dragonfly/pull/8350)). - Fixed a crash in blocking commands when a watched key holds a value of the wrong type. The registered blocked keys are now cleaned up ([#8305](https://github.com/dragonflydb/dragonfly/pull/8305)). - Fixed a crash when restoring an HNSW vector index while a key is being deleted concurrently ([#8466](https://github.com/dragonflydb/dragonfly/pull/8466)). - Fixed ACL permission checks for commands that both read and write keys (such as `COPY` or `LMOVE`). Source keys are now checked for read access and destination keys for write access ([#8249](https://github.com/dragonflydb/dragonfly/pull/8249)). - Fixed `INFO persistence` reporting `rdb_bgsave_in_progress:1` forever after a `BGSAVE`. `rdb_last_bgsave_status` is now also updated when a background save finishes ([#8459](https://github.com/dragonflydb/dragonfly/pull/8459)). - In emulated cluster mode, replicas now advertise the master's announced address in `CLUSTER NODES`/`SLOTS`/`SHARDS`, instead of the address passed to `REPLICAOF` ([#8241](https://github.com/dragonflydb/dragonfly/pull/8241)). - The daily version check now also sends anonymous deployment info: architecture, I/O backend, cloud provider, thread count, kernel version, uptime and a `maxmemory` bucket. No keys, data, hostnames or addresses are sent. ([#8469](https://github.com/dragonflydb/dragonfly/pull/8469)). Full Changelog: [v2.0.0...v2.0.2](https://github.com/dragonflydb/dragonfly/compare/v2.0.0...v2.0.2) </details>

Wuast94 added 1 commit 2026-10-08 00:41:18 +02:00

chore: update ghcr.io/dragonflydb/dragonfly (v2.0.0 → v2.0.2) 7c39e78f6d

Wuast94 scheduled this pull request to auto merge when all checks succeed 2026-10-08 00:41:46 +02:00

Wuast94 force-pushed updatarr/ghcr.io-dragonflydb-dragonfly-ec4d682d68 from 7c39e78f6d to bd21d3d224 2026-10-08 01:43:35 +02:00 Compare

Wuast94 force-pushed updatarr/ghcr.io-dragonflydb-dragonfly-ec4d682d68 from bd21d3d224 to 10f27439c8 2026-10-08 04:09:32 +02:00 Compare

Wuast94 merged commit bf1d10508c into main 2026-10-08 04:37:54 +02:00

Wuast94 referenced this pull request from a commit 2026-10-08 04:37:56 +02:00

Merge pull request 'chore: update ghcr.io/dragonflydb/dragonfly (v2.0.0 → v2.0.2)' (#396) from updatarr/ghcr.io-dragonflydb-dragonfly-ec4d682d68 into main

Wuast94 deleted branch updatarr/ghcr.io-dragonflydb-dragonfly-ec4d682d68 2026-10-08 04:37:56 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

vault/linkus!396

No description provided.