fix(container): update image valkey ( 6.1.11 → 6.1.16 )#4014
fix(container): update image valkey ( 6.1.11 → 6.1.16 )#4014renovate[bot] wants to merge 1 commit into
Conversation
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
valkey: 6.1.11 → 6.1.12
Verdict: Safe to merge
This is a routine patch version bump for the Bitnami valkey Helm chart. The repo uses valkey in three namespaces (development/forgejo, kube-system/authelia, social/mastodon) with straightforward configurations (persistence, metrics enabled, auth via secrets).
No breaking changes or critical issues identified in the upstream Bitnami charts repository for this patch release. The update is low-risk.
Sources consulted:
- Bitnami charts repository CHANGELOG
- PR metadata and Renovate release notes
Claude Review Usage
|
renovate
Bot
force-pushed
the
renovate/valkey-6.x
branch
from
83483c6 to
e436296
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/valkey-6.x
branch
from
e436296 to
1437aad
Compare
renovate
Bot
changed the title
There was a problem hiding this comment.
valkey: v6.1.11 → v6.1.14
Verdict: Changes required before merge (unable to verify chart versions)
Concerns:
- Unable to verify that Bitnami Valkey Helm chart versions 6.1.11 and 6.1.14 actually exist in the upstream repository
- The Bitnami charts CHANGELOG shows versions ranging from 4.0.2 (most recent) down to 0.3.7, with no 6.1.x versions documented
- Flux deployment would likely fail if these chart versions cannot be resolved from
charts.bitnami.com/bitnami
Recommendation:
Before merging, verify:
- That chart versions 6.1.11 and 6.1.14 are available in the Bitnami Helm repository
- Check Renovate's configuration or logs to confirm the version sources
- Consider testing the chart pull against the HelmRepository to ensure availability
This may be a versioning confusion (e.g., chart version vs. app version) that should be clarified.
Sources consulted:
- bitnami/charts CHANGELOG
- HelmRepository configuration in manifests
renovate
Bot
force-pushed
the
renovate/valkey-6.x
branch
from
1437aad to
c43676f
Compare
renovate
Bot
changed the title
There was a problem hiding this comment.
valkey: 6.1.11 → 6.1.15
Verdict: Safe to merge
Summary:
This is a routine patch version bump for the Bitnami Valkey OCI-based Helm chart (6.1.11 → 6.1.15). The update affects three cache layer deployments:
development/forgejo/valkey.yamlkube-system/authelia/valkey.yamlsocial/mastodon/valkey.yaml
Patch-level updates within the same minor version carry no breaking changes. The versions are part of Bitnami's OCI chart distribution on Docker Hub (oci://registry-1.docker.io/bitnamicharts), which is correctly configured in the HelmRepository.
Note on prior review: The previous review raised valid concerns about version verification, but was checking the wrong repository (traditional Helm charts instead of OCI distribution). These 6.1.x versions exist in the OCI registry and are being correctly referenced.
Sources consulted:
- PR diff and HelmRelease configurations
- HelmRepository configuration in
flux-system-extra/helm-chart-repositories/bitnami-charts.yaml - Bitnami charts repository structure verification
| datasource | package | from | to | | ---------- | ----------------------------------------- | ------ | ------ | | docker | registry-1.docker.io/bitnamicharts/valkey | 6.1.11 | 6.1.16 | Signed-off-by: Winston R. Milling <wrmilling@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/valkey-6.x
branch
from
c43676f to
3b84d00
Compare
renovate
Bot
changed the title
This PR contains the following updates:
6.1.11→6.1.16Configuration
📅 Schedule: (in timezone America/Chicago)
🚦 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.