Renovate agent review for #100: feat(container)!: Update image docker.io/valkey/valkey ( 8.1.7 ➔ 9.0.4 ) #79
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
webgrip/homelab-cluster#79
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @Ryangr0 on GitHub.
Originally assigned to: @Ryangr0, @Copilot on GitHub.
Renovate dependency review task
Marker:
renovate-agent-review:webgrip/homelab-cluster#100Review pull request: https://github.com/webgrip/homelab-cluster/pull/100
Repository:
webgrip/homelab-clusterPull request: #100
Title: feat(container)!: Update image docker.io/valkey/valkey ( 8.1.7 ➔ 9.0.4 )
Author: @webgrip-renovate[bot]
Base branch:
mainTask
Use the
renovate-reviewercustom agent instructions to produce the dependency update review for the linked pull request.Do not rely only on the context in this issue. Fetch the live PR metadata, changed files, diff, relevant repository files, and upstream release notes/changelogs/advisories yourself before writing the review.
To post or update the PR comment use the
github-writerMCP tools. Do not create a pull request, branch, or commit — not even as a fallback if posting the comment fails. If you cannot post the comment, add a comment to this tracking issue explaining why.Post or update exactly one comment on https://github.com/webgrip/homelab-cluster/pull/100. The first line of the comment body must be the literal sentinel
<!-- renovate-ai-review -->.If a PR comment containing that sentinel already exists, update it instead of creating a duplicate.
Do not modify repository files, push commits, open a code-change pull request, approve, merge, close, or retitle the pull request.
After posting or updating the PR comment, close this tracking issue as completed.
Initial changed files snapshot
kubernetes/apps/searxng/searxng/app/valkey.yaml(+1 -1)Initial PR body snapshot
This PR contains the following updates:
8.1.7→9.0.49.1.0⚠️ Major update: review upstream migration notes, chart values, and rollout impact before merging.
Release Notes
valkey-io/valkey (docker.io/valkey/valkey)
v9.0.4Compare Source
Upgrade urgency SECURITY: This release includes security fixes we recommend you
apply as soon as possible.
Security fixes
v9.0.3Compare Source
Valkey 9.0.3
Upgrade urgency SECURITY: This release includes security fixes we recommend you
apply as soon as possible.
Security fixes
Bug fixes
v9.0.2Compare Source
Upgrade urgency HIGH: There are critical bugs that may affect a subset of users.
Bug fixes
Performance/Efficiency Improvements
This makes it possible to mitigate a performance regression in 9.0.1 caused by the bug fix #2652.
Full Changelog: https://github.com/valkey-io/valkey/compare/9.0.1...9.0.2
v9.0.1Compare Source
Upgrade urgency MODERATE: Program an upgrade of the server, but it's not urgent.
Bug fixes
Full Changelog: https://github.com/valkey-io/valkey/compare/9.0.0...9.0.1
v9.0.0Compare Source
Valkey 9.0.0 GA - October 21, 2025
Upgrade urgency LOW: This is the first release of Valkey 9.0 which
includes stability, bug fixes, and incremental improvements over the third release candidate.
Bug fixes
For a high level overview of the release, you can checkout release blog
For the full set of changes for the releases, please review the previous release candidates rc1, rc2 and rc3.
Configuration
📅 Schedule: (in timezone Europe/Amsterdam)
🚦 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.