fix(container): update image ghcr.io/valkey-io/valkey ( 9.0.1 → 9.0.2 )

[renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/valkey-io/valkey	patch	9.0.1 → 9.0.2

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

valkey-io/valkey (ghcr.io/valkey-io/valkey)

v9.0.2

Compare Source

Upgrade urgency HIGH: There are critical bugs that may affect a subset of users.

Bug fixes

• Avoid memory leak of new argv when HEXPIRE commands target only non-exiting fields (#​2973)
• Fix HINCRBY and HINCRBYFLOAT to update volatile key tracking (#​2974)
• Avoid empty hash object when HSETEX added no fields (#​2998)
• Fix case-sensitive check for the FNX and FXX arguments in HSETEX (#​3000)
• Prevent assertion in active expiration job after a hash with volatile fields is overwritten (#​3003, #​3007)
• Fix HRANDFIELD to return null response when no field could be found (#​3022)
• Fix HEXPIRE to not delete items when validation rules fail and expiration is in the past (#​3023, #​3048)
• Fix how hash is handling overriding of expired fields overwrite (#​3060)
• HSETEX - Always issue keyspace notifications after validation (#​3001)
• Make zero a valid TTL for hash fields during import mode and data loading (#​3006)
• Trigger prepareCommand on argc change in module command filters (#​2945)
• Restrict TTL from being negative and avoid crash in import-mode (#​2944)
• Fix chained replica crash when doing dual channel replication (#​2983)
• Skip slot cache optimization for AOF client to prevent key duplication and data corruption (#​3004)
• Fix used_memory_dataset underflow due to miscalculated used_memory_overhead (#​3005)
• Avoid duplicate calculations of network-bytes-out in slot stats with copy-avoidance (#​3046)
• Fix XREAD returning error on empty stream with + ID (#​2742)

Performance/Efficiency Improvements

• Track reply bytes in I/O threads if commandlog-reply-larger-than is -1 (#​3086, #​3126).
  This makes it possible to mitigate a performance regression in 9.0.1 caused by the bug fix #​2652.

Full Changelog: valkey-io/valkey@9.0.1...9.0.2

---

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.

[mglants-bot]

--- kubernetes/subterra/apps/apps/remnawave/app Kustomization: flux-system/remnawave HelmRelease: apps/remnawave

+++ kubernetes/subterra/apps/apps/remnawave/app Kustomization: flux-system/remnawave HelmRelease: apps/remnawave

@@ -246,13 +246,13 @@

         containers:
           redis:
             env:
               VALKEY_EXTRA_FLAGS: --requirepass valkey
             image:
               repository: ghcr.io/valkey-io/valkey
-              tag: 9.0.1
+              tag: 9.0.2
             resources:
               limits:
                 memory: 128Mi
               requests:
                 cpu: 5m
                 memory: 32Mi