Skip to content

Update docker.io/valkey/valkey Docker tag#39

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/docker.io-valkey-valkey-9.x
Open

Update docker.io/valkey/valkey Docker tag#39
renovate[bot] wants to merge 1 commit intomainfrom
renovate/docker.io-valkey-valkey-9.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 17, 2026

This PR contains the following updates:

Package Type Update Change
docker.io/valkey/valkey image minor 9.09.1
docker.io/valkey/valkey image patch 9.0.3-alpine9.0.4-alpine

Release Notes

valkey-io/valkey (docker.io/valkey/valkey)

v9.0.4

Compare Source

Upgrade urgency SECURITY: This release includes security fixes we recommend you
apply as soon as possible.

Security fixes
  • (CVE-2026-23479) Use-After-Free in unblock client flow
  • (CVE-2026-25243) Invalid Memory Access in RESTORE command
  • (CVE-2026-23631) Use-after-free when full sync occurs during a yielding Lua/function execution

Configuration

📅 Schedule: (in timezone UTC)

  • 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 is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot force-pushed the renovate/docker.io-valkey-valkey-9.x branch from 5378aee to 2b4d2ab Compare May 6, 2026 22:37
@renovate renovate Bot changed the title Update docker.io/valkey/valkey Docker tag to v9.1 Update docker.io/valkey/valkey Docker tag May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants