Conversation
Signed-off-by: cozystack-bot <[email protected]>
cozystack-bot
requested review from
klinch0,
kvaps and
lllamnyp
as code owners
WalkthroughBulk update of container image tags and digests across apps, core, extra, and system packages, advancing many components from v0.36.0-beta.1 to v0.36.0-beta.2 and refreshing several pinned digests. No logic, API, or configuration structure changes beyond version/digest values and one version string field. Changes
Sequence Diagram(s)Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
![gemini-code-assist[bot]](proxy.php?url=https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @cozystack-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request is dedicated to preparing the v0.36.0-beta.2 release. It systematically updates all internal references to component versions and associated container image SHAs to align with the new beta release, ensuring consistency across the codebase for the upcoming deployment.
Highlights
- Version Updates: All relevant image tags and application versions across various components have been updated to
v0.36.0-beta.2. - Image SHA Changes: Numerous container image SHAs have been updated to reflect the new
v0.36.0-beta.2release for components likenginx-cache,kubevirt-csi-driver,installer,e2e-sandbox,matchbox,objectstorage-sidecar,s3manager,cozystack-api,cozystack-controller,dashboard,kubeapps-apis,kamaji,kubeovn-webhook,kubeovn, andobjectstorage-controller.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
This pull request prepares for the v0.36.0-beta.2 release by updating various version numbers and image digests across the codebase. The changes are mostly correct and consistent with a release process. However, I've found one inconsistency in packages/system/dashboard/values.yaml where an image tag was updated but its corresponding digest was not, which could lead to issues. Please see the specific comment for details.
| registry: ghcr.io/cozystack/cozystack | ||
| repository: dashboard | ||
| tag: v0.36.0-beta.1 | ||
| tag: v0.36.0-beta.2 |
There was a problem hiding this comment.
While the image tag has been updated to v0.36.0-beta.2, the corresponding digest on the next line has not been updated. It still points to the digest of the previous version. This can lead to image pull inconsistencies. Please update the digest as well.
![coderabbitai[bot]](proxy.php?url=https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml (1)
79-79: Optional: Template appVersion from the Chart
Replace the hardcoded version with{{ .Chart.AppVersion }}to keep releases in sync—verification shows this is the only occurrence.- "appVersion": "v0.36.0-beta.2", + "appVersion": "{{ .Chart.AppVersion }}",
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (17)
packages/apps/http-cache/images/nginx-cache.tag(1 hunks)packages/apps/kubernetes/images/kubevirt-csi-driver.tag(1 hunks)packages/core/installer/values.yaml(1 hunks)packages/core/testing/values.yaml(1 hunks)packages/extra/bootbox/images/matchbox.tag(1 hunks)packages/extra/seaweedfs/images/objectstorage-sidecar.tag(1 hunks)packages/system/bucket/images/s3manager.tag(1 hunks)packages/system/cozystack-api/values.yaml(1 hunks)packages/system/cozystack-controller/values.yaml(1 hunks)packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml(1 hunks)packages/system/dashboard/values.yaml(2 hunks)packages/system/kamaji/values.yaml(2 hunks)packages/system/kubeovn-webhook/values.yaml(1 hunks)packages/system/kubeovn/values.yaml(1 hunks)packages/system/kubevirt-csi-node/values.yaml(1 hunks)packages/system/objectstorage-controller/values.yaml(1 hunks)packages/system/seaweedfs/values.yaml(1 hunks)
🔇 Additional comments (18)
packages/extra/seaweedfs/images/objectstorage-sidecar.tag (1)
1-1: Approve sidecar bump to v0.36.0-beta.2
Verified no lingering v0.36.0-beta.1 references.packages/system/bucket/images/s3manager.tag (1)
1-1: Approve s3manager digest refresh
All consumers (deployment template and Makefile) now reference the updated images/s3manager.tag and no stale digests remain.packages/system/cozystack-api/values.yaml (1)
2-2: Approve cozystack-api image pinned to v0.36.0-beta.2 Verified no leftover v0.36.0-beta.1 references in the codebase.packages/apps/kubernetes/images/kubevirt-csi-driver.tag (1)
1-1: Approve digest update: node and app references match
Node-sidevalues.yamlinpackages/system/kubevirt-csi-nodereferences the samesha256:8eb9803aa1b38e1b2db98237bf0d1046f0ba90be0157c22da1efc3811bb25ecfas the updated tag. No further changes required.packages/system/dashboard/values.yaml (2)
22-22: Dashboard image tag bumped to v0.36.0-beta.2 — looks good.
51-52: Tag/digest consistency check passed. Nov0.36.0-beta.1remnants found and allv0.36.0-beta.2tags are properly paired with a digest.packages/apps/http-cache/images/nginx-cache.tag (1)
1-1: nginx-cache digest bump — looks good.packages/system/kubeovn/values.yaml (1)
67-67: Chart renders the tag value verbatim; including@sha256:…inglobal.images.kubeovn.tagyields a validrepository:v1.14.5@sha256:…image reference.packages/system/seaweedfs/values.yaml (1)
127-127: SeaweedFS COSI sidecar bumped to v0.36.0-beta.2 — looks good.packages/extra/bootbox/images/matchbox.tag (1)
1-1: matchbox moved to v0.36.0-beta.2 with pinned digest — looks good.packages/system/kamaji/values.yaml (1)
6-6: Unable to confirm digest via script – manual verification required
Fallback curl didn’t return a Docker-Content-Digest header; please verify that GHCR’s digest for cozystack/cozystack/kamaji:v0.36.0-beta.2 (including migrate-image) matches
sha256:f901f5212e4883ee014dff3ac75a9ed91d136b71dd955b34c12539840e4454ea
—for example, by running:docker pull ghcr.io/cozystack/cozystack/kamaji:v0.36.0-beta.2 docker inspect --format='{{index .RepoDigests 0}}' ghcr.io/cozystack/cozystack/kamaji:v0.36.0-beta.2packages/system/kubevirt-csi-node/values.yaml (1)
3-3: Digest-only refresh verified; digests match the tag file elsewhere.packages/system/kubeovn-webhook/values.yaml (1)
3-3: kubeovn-webhook image digest unresolved; manually verify ghcr.io/cozystack/cozystack/kubeovn-webhook:v0.36.0-beta.2 matches sha256:8e67b2971f8c079a8b0636be1d091a9545d6cb653d745ff222a5966f56f903bd (e.g. via GET manifest orskopeo inspect).packages/system/objectstorage-controller/values.yaml (1)
3-3: Verify objectstorage-controller image digest
Manually confirm the digest for v0.36.0-beta.2 matches
sha256:61111863bc66293d71e131bfa8fa91569a80885bf2805e7e21bb2c9d780848e5using a manifest GET, for example:curl -s \ -H 'Accept:application/vnd.docker.distribution.manifest.v2+json' \ https://ghcr.io/v2/cozystack/cozystack/objectstorage-controller/manifests/v0.36.0-beta.2 \ | jq -r '.config.digest'Standardize quoting (e.g., use single quotes) for all image entries in values.yaml.
packages/core/installer/values.yaml (1)
2-2: Installer image digest could not be resolved; please manually verify
Thecurl -sIrequest returned an emptyDocker-Content-Digest. Confirm that the pinned digest (sha256:c9b197736d4e0bcf5ed74ed771d6408a6ea09b0451a3871469a1977eb849bef1) matchesghcr.io/cozystack/cozystack/installer:v0.36.0-beta.2, or adjust the manifest request headers/mechanism to correctly retrieve the digest.packages/core/testing/values.yaml (1)
2-2: Manual verification needed: digest unresolved for e2e-sandbox
The script failed to fetch the Docker-Content-Digest forcozystack/cozystack/e2e-sandbox:v0.36.0-beta.2—manually confirm that this tag corresponds tosha256:3ad75dec04d2e056857fc9b4fb94f2e443c12a7e715cc78c854fe652520a5f30on GHCR, and likewise verify the controller image digest.packages/system/cozystack-controller/values.yaml (2)
2-2: LGTM: controller image tag+digest bumped to v0.36.0-beta.2.
5-5: LGTM: cozystackVersion aligned with image tag.
2 participants
This PR prepares the release
v0.36.0-beta.2.Summary by CodeRabbit