Release v0.38.2 - #1678
Conversation
Signed-off-by: cozystack-bot <217169706+cozystack-bot@users.noreply.github.com>
WalkthroughContainer image references are updated from v0.38.1 to v0.38.2 across the cozystack installer, testing, and system packages, including dashboard, controllers, and supporting services, with corresponding sha256 digest changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Rationale: All changes follow an identical, homogeneous pattern of version and digest bumps across multiple files with no functional logic, control flow modifications, or behavioral changes. The large set of repetitive updates requires minimal cognitive effort to verify consistency. Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (16)
🧰 Additional context used🧠 Learnings (3)📓 Common learnings📚 Learning: 2025-06-26T04:29:24.830ZApplied to files:
📚 Learning: 2025-07-11T06:11:25.438ZApplied to files:
⏰ 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)
🔇 Additional comments (16)
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. Comment |
Summary of ChangesHello Cozystack Bot (@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 for the Highlights
Using Gemini Code AssistThe 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 by creating a comment using either
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 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 (@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
|
There was a problem hiding this comment.
Code Review
This pull request prepares for the v0.38.2 release by updating various image tags and versions across the project. The changes are mostly straightforward version bumps. However, I've noticed a few inconsistencies in the image tagging that could be improved for better release management and clarity. Specifically, some images have been re-tagged with the new version but share the same SHA digest as the previous version, while another has a new digest but an unchanged version tag. My review includes suggestions to address these points to ensure versioning is consistent and traceable.
| @@ -1 +1 @@ | |||
| ghcr.io/cozystack/cozystack/s3manager:v0.5.0@sha256:ec77d572175945f6be3e3da6f77fa8a5988cce33ae2425e71a9012ed84cf439f | |||
| ghcr.io/cozystack/cozystack/s3manager:v0.5.0@sha256:3825c9b4b6238f88f1b0de73bd18866a7e5f83f178d28fe2830f3bf24efb187d | |||
There was a problem hiding this comment.
The image digest has been updated, but the version tag remains v0.5.0. This is inconsistent with the changes and the overall release version v0.38.2. When an image's content changes (indicated by the new SHA digest), its version tag should also be updated to reflect the change (e.g., a patch version bump to v0.5.1). This is crucial for clear version tracking and to avoid deployment issues where an old cached image with the same tag might be used.
ghcr.io/cozystack/cozystack/s3manager:v0.5.1@sha256:3825c9b4b6238f88f1b0de73bd18866a7e5f83f178d28fe2830f3bf24efb187d
| image: ghcr.io/cozystack/cozystack/openapi-ui-k8s-bff:v0.38.2@sha256:7ffd8ae7b9da73fec7ae61a71c9c821a718d89a1b1df0197e09fda57678e1220 | ||
| tokenProxy: | ||
| image: ghcr.io/cozystack/cozystack/token-proxy:v0.38.1@sha256:fad27112617bb17816702571e1f39d0ac3fe5283468d25eb12f79906cdab566b | ||
| image: ghcr.io/cozystack/cozystack/token-proxy:v0.38.2@sha256:fad27112617bb17816702571e1f39d0ac3fe5283468d25eb12f79906cdab566b |
There was a problem hiding this comment.
The tokenProxy image tag has been bumped to v0.38.2, but its SHA256 digest is identical to the one from v0.38.1. This suggests the image was re-tagged without being rebuilt. For release integrity and traceability, each release tag should correspond to a unique image digest, which is typically achieved by rebuilding the image as part of the release process. Using the same digest for different tags can lead to confusion and potential issues with deployment rollouts if not handled carefully by Kubernetes.
| objectstorage: | ||
| controller: | ||
| image: "ghcr.io/cozystack/cozystack/objectstorage-controller:v0.38.1@sha256:7d37495cce46d30d4613ecfacaa7b7f140e7ea8f3dbcc3e8c976e271de6cc71b" | ||
| image: "ghcr.io/cozystack/cozystack/objectstorage-controller:v0.38.2@sha256:7d37495cce46d30d4613ecfacaa7b7f140e7ea8f3dbcc3e8c976e271de6cc71b" |
There was a problem hiding this comment.
The objectstorage-controller image tag has been bumped to v0.38.2, but its SHA256 digest is identical to the one from v0.38.1. This suggests the image was re-tagged without any changes. For release integrity and traceability, each release tag should correspond to a unique image digest. Using the same digest for different tags can cause confusion and issues with deployment rollouts.
This PR prepares the release
v0.38.2.Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.