Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.22.1 ) #369

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 1, 2024

This PR contains the following updates:

Package Update Change
ghcr.io/dragonflydb/dragonfly minor v1.19.0 -> v1.22.1

Release Notes

dragonflydb/dragonfly (ghcr.io/dragonflydb/dragonfly)

v1.22.1

Compare Source

Dragonfly v1.22.1

This is a patch release. Urgency to update: low

fix: infinite recursive calls in the allocation tracker #​3665

Full Changelog: dragonflydb/dragonfly@v1.22.0...v1.22.1

v1.22.0

Compare Source

Dragonfly v1.22.0

Some prominent changes include:

  • Lots of stability fixes around JSON and Search APIS:
    #​3459, #​3284, #​3537, #​3544,#​3580, #​3582, #​3578, #​3591, #​3597, #​3539
  • Support HELLO AUTH handshake: #​3486
  • Implement FT.TAGVALS: #​3493
  • Introduce Dragonfly specific lua pragmas: #​3517
  • Memcache now replicates flags correctly: #​3538
  • Memcache API now supports absolute timestamps as well: #​3607
  • PEXPIRETIME and EXPIRETIME are implemented by @​Eunoia1729 - thank you!
  • Last but not least, a significant contribution by @​cunla: a massive test suite, likely the largest in Dragonfly's history, with 12K lines of code. This contribution has sparked further efforts to enhance Dragonfly's compatibility and stability. The initial results are included in this release.
What's Changed
New Contributors

Full Changelog: dragonflydb/dragonfly@v1.21.0...v1.22.0

v1.21.4

Compare Source

Dragonfly v1.21.4

This is a patch release.

chore: fix search replication (#​3547)

v1.21.3

Compare Source

Dragonfly v1.21.3

This is a patch release.

fix: display real replica remote address in INFO logs
fix: crash with concurrent multi-shard BLMOVE operations #​3540

This follows up on Dragonfly v1.21.2 release.

v1.21.2

Compare Source

Dragonfly v1.21.2

This is a patch release.

fix: disable code that can cause potential deadlocks during the replication (#​3521)

This follows up on Dragonfly v1.21.0 release, that includes the following prominent features:

  • Alpha release of SSD Data tiering - enabled with flag --tiered_prefix some/path/basename
  • Very basic support of multi-tenancy #​3260
  • HSETEX now supports NX option, see our docs.
  • Added support for JSON.MERGE and for JSON.MSET.
  • valkey's replica-announce-ip and --cluster--announc--ip are consolidated via --announce-ip flag.

Full Changelog: dragonflydb/dragonfly@v1.21.1...v1.21.2

v1.21.1

Compare Source

Dragonfly v1.21.1

This is a patch release.

fix: the replication from older masters to newer versions (#​3473)

This follows up on Dragonfly v1.21.0 release, that includes the following prominent features:

  • Alpha release of SSD Data tiering - enabled with flag --tiered_prefix some/path/basename
  • Very basic support of multi-tenancy @​3260
  • HSETEX now supports NX option, see our docs.
  • Added support for JSON.MERGE and for JSON.MSET.
  • valkey's replica-announce-ip and --cluster--announc--ip are consolidated via --announce-ip flag.

v1.21.0

Compare Source

Dragonfly v1.21.0

Some prominent changes include:

  • Alpha release of SSD Data tiering - enabled with flag --prefix some/path/basename
  • Very basic support of multi-tenancy @​3260
  • HSETEX now supports NX option, see our docs.
  • Added support for JSON.MERGE and for JSON.MSET.
  • valkey's replica-announce-ip and --cluster--announc--ip are consolidated via --announce-ip flag.
What's Changed

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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch from 235f93e to 09028fe Compare July 2, 2024 12:32
@renovate renovate bot changed the title fix(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.19.1 ) fix(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.19.2 ) Jul 2, 2024
@renovate renovate bot force-pushed the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch from 09028fe to d3b861e Compare July 9, 2024 14:08
@renovate renovate bot changed the title fix(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.19.2 ) feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.20.0 ) Jul 9, 2024
@renovate renovate bot force-pushed the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch from d3b861e to 22e49be Compare July 10, 2024 04:55
@renovate renovate bot changed the title feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.20.0 ) feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.20.1 ) Jul 10, 2024
@renovate renovate bot force-pushed the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch from 22e49be to 07635ba Compare August 7, 2024 10:08
@renovate renovate bot changed the title feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.20.1 ) feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.0 ) Aug 7, 2024
@renovate renovate bot force-pushed the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch from 07635ba to 161120d Compare August 9, 2024 15:04
@renovate renovate bot changed the title feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.0 ) feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.1 ) Aug 9, 2024
@renovate renovate bot force-pushed the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch from 161120d to b01f91f Compare August 16, 2024 04:08
@renovate renovate bot changed the title feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.1 ) feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.2 ) Aug 16, 2024
@renovate renovate bot changed the title feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.2 ) feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.3 ) Aug 22, 2024
@renovate renovate bot force-pushed the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch 2 times, most recently from 01aea57 to 3eae525 Compare August 23, 2024 10:44
@renovate renovate bot changed the title feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.3 ) feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.4 ) Aug 23, 2024
@renovate renovate bot force-pushed the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch from 3eae525 to c181938 Compare September 3, 2024 15:45
@renovate renovate bot changed the title feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.21.4 ) feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.22.0 ) Sep 3, 2024
@renovate renovate bot force-pushed the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch from c181938 to 3331276 Compare September 8, 2024 13:20
@renovate renovate bot changed the title feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.22.0 ) feat(container): update ghcr.io/dragonflydb/dragonfly ( v1.19.0 → v1.22.1 ) Sep 8, 2024
@brettinternet brettinternet merged commit 3cc82bf into main Sep 10, 2024
2 of 5 checks passed
@brettinternet brettinternet deleted the renovate/main-ghcr.io-dragonflydb-dragonfly-1.x branch September 10, 2024 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant