Skip to content

chore: update valkey source and version - #1179

Open
skourta wants to merge 4 commits into
canonical:mainfrom
skourta:update-valkey-repo
Open

chore: update valkey source and version#1179
skourta wants to merge 4 commits into
canonical:mainfrom
skourta:update-valkey-repo

Conversation

@skourta

@skourta skourta commented Aug 18, 2026

Copy link
Copy Markdown

Description

Update the valkey image source to the new valkey artifacts meta-repository and version to 7.2.13.

@zhijie-yang zhijie-yang left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zhijie-yang zhijie-yang changed the title patch: update valkey source and version chore: update valkey source and version Aug 19, 2026
@skourta

skourta commented Aug 25, 2026

Copy link
Copy Markdown
Author

@zhijie-yang can you please re-trigger the build. The metrics exporter which had the CVEs has been rebuilt with a patched go version.

@zhijie-yang

Copy link
Copy Markdown
Collaborator

the CI is triggered by your commit. let's see if this passes.

@skourta

skourta commented Aug 26, 2026

Copy link
Copy Markdown
Author

@zhijie-yang green CI

@zhijie-yang zhijie-yang left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes! The following comment is generated using the AGENTS.md in the feature branch in OpenCode with the GPT-5.6 Sol (xhigh effort). I affirm all the comments are legit.


The source bump introduces release-policy and recipe blockers.

oci/valkey/documentation.yaml:8 — [blocker] The source migration leaves the published issues and source-code links pointing to canonical/charmed-valkey-rock; update them to the new canonical/valkey-artifacts repository. (§5)

The latest vulnerability scan is clean: https://github.com/canonical/oci-factory/actions/runs/32855920817/job/97846045027

Comment thread oci/valkey/image.yaml
directory: ./valkey/rocks/standard
release:
7.2.12-24.04:
7.2.13-24.04:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[blocker] This modified SemVer track includes the patch component; use 7.2-24.04 rather than 7.2.13-24.04. (§3)

Suggested change
7.2.13-24.04:
7.2-24.04:

Comment thread oci/valkey/image.yaml
7.2.13-24.04:
end-of-life: "2029-04-01T00:00:00Z"
risks:
- stable

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[blocker] This is the first release of a new track, so it must start with edge only rather than stable. (§3)

Suggested change
- stable
- edge

Comment thread oci/valkey/image.yaml
- source: "canonical/valkey-artifacts"
commit: 252920e17d56e097efd0323e26a4ebdcb68312d7
directory: ./valkey/rocks/standard
release:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[blocker] The pinned recipe stages .deb packages (lines 51-54), but its manifest part (lines 98-106) is hand-written. Please use https://github.com/canonical/rocks-security-manifest, wired exactly as its README specifies. (§4)

Comment thread oci/valkey/image.yaml
directory: .
- source: "canonical/valkey-artifacts"
commit: 252920e17d56e097efd0323e26a4ebdcb68312d7
directory: ./valkey/rocks/standard

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[blocker] This source bump drops the previous recipe’s redis_exporter part (old lines 49-57) and replaces it with a staged package. Is this intentional? Please confirm it is not a regression, or restore the part. (§4)

@zhijie-yang zhijie-yang added rock/new A new rock and removed pending cve labels Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rock/new A new rock

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants