Conversation
Signed-off-by: cozystack-bot <[email protected]>
cozystack-bot
requested review from
klinch0,
kvaps and
lllamnyp
as code owners
WalkthroughBumps multiple container image tags and/or digests across Helm values and tag files from v0.36.0-alpha.2 to v0.36.0-beta.1, plus one digest-only update for s3manager. No structural changes, logic changes, or new fields were introduced. Changes
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 system for the v0.36.0-beta.1 release. It systematically updates all internal references to component images and application versions, ensuring that the entire stack points to the newly built beta artifacts. This is a standard procedure for advancing the project through its release cycle.
Highlights
- Version Bump: All relevant internal component image tags and application versions have been updated from
v0.36.0-alpha.2tov0.36.0-beta.1. - Image SHA Updates: Corresponding SHA256 digests for all updated container images have been refreshed to reflect the new beta builds.
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.1 release by updating version numbers and image tags across multiple configuration files. The review has identified two critical issues where image tags were updated but their corresponding SHA256 digests were not, which would result in deploying outdated container images. These need to be corrected to ensure the release contains the correct artifacts.
| @@ -1,2 +1,2 @@ | |||
| cozystackAPI: | |||
| image: ghcr.io/cozystack/cozystack/cozystack-api:v0.36.0-alpha.2@sha256:c545ecf298ce5f70d947ba3b9cbdb4415d540e62b1e991984bc8847db8e1943c | |||
| image: ghcr.io/cozystack/cozystack/cozystack-api:v0.36.0-beta.1@sha256:c545ecf298ce5f70d947ba3b9cbdb4415d540e62b1e991984bc8847db8e1943c | |||
There was a problem hiding this comment.
The image tag has been updated to v0.36.0-beta.1, but the SHA256 digest has not been changed. This will result in pulling the old image version (v0.36.0-alpha.2). Please update the digest to match the new image version.
| tag: v0.36.0-beta.1 | ||
| digest: "sha256:54906b3d2492c8603a347a5938b6db36e5ed5c4149111cae1804ac9110361947" |
There was a problem hiding this comment.
The image tag has been updated to v0.36.0-beta.1, but the digest on the next line has not been updated. When both tag and digest are specified, the digest takes precedence, which will result in deploying the old image. Please update the digest to match the new version.
![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: 1
🧹 Nitpick comments (1)
packages/core/testing/values.yaml (1)
2-2: LGTM: e2e sandbox image updatedIf CI caches images, consider forcing a pull to pick up the new digest.
📜 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 (13)
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/objectstorage-controller/values.yaml(1 hunks)packages/system/seaweedfs/values.yaml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Prepare environment
🔇 Additional comments (12)
packages/system/seaweedfs/values.yaml (1)
123-123: Approved: sidecar image matches tag file
Images in packages/system/seaweedfs/values.yaml and packages/extra/seaweedfs/images/objectstorage-sidecar.tag are in sync.packages/system/objectstorage-controller/values.yaml (1)
3-3: LGTM: controller image bumped and digest-pinnedNo issues spotted.
packages/system/kubeovn-webhook/values.yaml (1)
3-3: LGTM: kubeovn-webhook image to v0.36.0-beta.1No config changes needed here; rollout should be straightforward.
packages/extra/bootbox/images/matchbox.tag (1)
1-1: LGTM: matchbox image bumped and digest pinned.
No issues spotted.packages/core/installer/values.yaml (1)
2-2: LGTM: installer image moved to v0.36.0-beta.1 with new digest.
Looks consistent with the release bump.packages/extra/seaweedfs/images/objectstorage-sidecar.tag (1)
1-1: LGTM: objectstorage-sidecar updated to beta.1 with digest.
All good.packages/system/dashboard/values.yaml (2)
51-52: LGTM: kubeapps-apis tag and digest updated.
Pinned digest aligns with the version bump.
22-23: Manual verification required for dashboard image digest
Remote digest for tag v0.36.0-beta.1 couldn’t be fetched automatically—please confirm the tag→digest mapping and update thedigest:field if it differs; otherwise the image will remain pinned to the old digest.packages/system/cozystack-api/values.yaml (1)
2-2: Confirm or update image digest for cozystack-api v0.36.0-beta.1
Remote digest couldn’t be retrieved automatically (likely due to authentication); manually verify that ghcr.io/cozystack/cozystack/cozystack-api:v0.36.0-beta.1 resolves to sha256:c545ecf298ce5f70d947ba3b9cbdb4415d540e62b1e991984bc8847db8e1943c and update the digest if it has changed.packages/system/bucket/images/s3manager.tag (1)
1-1: Digest pin update looks correct; manual verification required
The digest-only refresh matches the intended tag, but authentication is needed to fetch the manifest digest from GHCR. Please verify locally using your registry credentials (for example:crane digest ghcr.io/cozystack/cozystack/s3manager:v0.5.0and confirm it equals
sha256:471c10b6373920924aa88d9dbab5306258a4d80748ab917c9430c0c7961d161b).packages/system/cozystack-controller/values.yaml (1)
2-2: Controller image & cozystackVersion set to v0.36.0-beta.1
No remaining v0.36.0-alpha.2 references; allcozystackVersionentries resolve tov0.36.0-beta.1(e.g. runrg -Po 'cozystackVersion:\s*"?\K[^"\s]+' | sort -u).packages/system/kamaji/values.yaml (1)
6-6: Update verification script to avoid line numbers
Drop the-nflag from bothrgcommands so they emit only the checksum, notline:checksum. After this change both invocations output715462d6f5a8d8dd2b1814aeba2dff86e8afb7e9d1eda1bde7ca39685a446286, confirming they match.
| "helmGlobalNamespace": {{ include "kubeapps.helmGlobalPackagingNamespace" . | quote }}, | ||
| "carvelGlobalNamespace": {{ .Values.kubeappsapis.pluginConfig.kappController.packages.v1alpha1.globalPackagingNamespace | quote }}, | ||
| "appVersion": "v0.36.0-alpha.2", | ||
| "appVersion": "v0.36.0-beta.1", |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Align appVersion across chart and values
Change looks good. Please confirm this "appVersion" matches the dashboard image tag and any Chart.yaml appVersion to avoid UI/version skew.
Run to check for leftover alpha.2 references and mismatches:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Leftover alpha.2 occurrences:"
rg -n 'v0\.36\.0-alpha\.2' || true
echo
echo "All 0.36.0 tags/digests in repo (sanity scan):"
rg -nP 'v0\.36\.0-(alpha|beta)\.\d+@sha256:[0-9a-f]{64}|v0\.36\.0-(alpha|beta)\.\d+' | sed 's/.*://'Length of output: 1124
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Chart.yaml version & appVersion:"
rg -n -e '^version:' -e '^appVersion:' -C0 packages/system/dashboard/charts/kubeapps/Chart.yaml || true
echo
echo "Dashboard values block (20 lines):"
rg -n 'dashboard:' -A20 packages/system/dashboard/charts/kubeapps/values.yaml || trueLength of output: 1569
Fix dashboard configmap appVersion
In packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml:79, change
- "appVersion": "v0.36.0-beta.1",
+ "appVersion": "2.12.0",to align with Chart.yaml’s appVersion (2.12.0) and values.yaml image.tag (2.12.0-debian-12-r0).
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "appVersion": "v0.36.0-beta.1", | |
| "appVersion": "2.12.0", |
🤖 Prompt for AI Agents
In packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml
around line 79, the configmap currently sets "appVersion": "v0.36.0-beta.1"
which is out of sync; update that value to "2.12.0" to match Chart.yaml’s
appVersion and ensure consistency with values.yaml image.tag
(2.12.0-debian-12-r0).
2 participants
This PR prepares the release
v0.36.0-beta.1.Summary by CodeRabbit