Skip to content

Conversation

cozystack-bot
Copy link
Member

@cozystack-bot cozystack-bot commented Aug 19, 2025

This PR prepares the release v0.35.1.

Summary by CodeRabbit

  • Version Update

    • Upgraded various system components from v0.35.0 to v0.35.1
    • Updated container image references and digests across multiple services
    • Includes updates to images for dashboard, API, controller, kamaji, kubeOVN, object storage, and other system components
  • Notes

    • No functional changes to the system
    • Only version and image digest updates

Signed-off-by: cozystack-bot <217169706+cozystack-bot@users.noreply.github.com>
@cozystack-bot cozystack-bot added the release Releasing a new Cozystack version label Aug 19, 2025
@cozystack-bot cozystack-bot added the release Releasing a new Cozystack version label Aug 19, 2025
Copy link
Contributor

coderabbitai bot commented Aug 19, 2025

Walkthrough

Bumps multiple container image tags and digests across core, system, extra, and app packages to v0.35.1 (or new digests), and updates related Helm values and a dashboard ConfigMap appVersion. No logic, templates, or control flow changes beyond value updates.

Changes

Cohort / File(s) Summary of changes
Core images → v0.35.1
packages/core/installer/values.yaml, packages/core/testing/values.yaml
Updated installer and e2e-sandbox images from v0.35.0 to v0.35.1 with new digests.
System images → v0.35.1
packages/system/cozystack-api/values.yaml, packages/system/cozystack-controller/values.yaml, packages/system/dashboard/values.yaml, packages/system/kamaji/values.yaml, packages/system/kubeovn-webhook/values.yaml, packages/system/objectstorage-controller/values.yaml, packages/system/seaweedfs/values.yaml
Bumped component images to v0.35.1; updated digests accordingly. Controller cozystackVersion updated to v0.35.1. Kamaji migrate-image arg updated to v0.35.1.
Dashboard template appVersion
packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml
Replaced two appVersion occurrences from v0.35.0 to v0.35.1.
Extra components → v0.35.1
packages/extra/bootbox/images/matchbox.tag, packages/extra/seaweedfs/images/objectstorage-sidecar.tag
Updated matchbox and objectstorage-sidecar tags from v0.35.0 to v0.35.1 with new digests.
Digest-only updates
packages/apps/http-cache/images/nginx-cache.tag, packages/system/kubeovn/values.yaml
Swapped image digests without changing version tags (nginx-cache 0.7.0 digest; kubeovn v1.13.14 digest).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • kvaps
  • lllamnyp
  • klinch0

Poem

I nudge the tags, hop to v0.35.1,
Digest crumbs aligned, my update run.
Charts and values, tidy in a row,
Version burrows deeper—off we go!
With whiskers twitching, CI will cheer,
🥕 Ship it swift—new images are here!

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


📜 Recent 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.

📥 Commits

Reviewing files that changed from the base of the PR and between c5b64af and 4d7992b.

📒 Files selected for processing (14)
  • packages/apps/http-cache/images/nginx-cache.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/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/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 (14)
packages/core/installer/values.yaml (1)

2-2: Installer image bump verified – no stale references to v0.35.0 found

  • packages/core/installer/values.yaml (line 2): image updated to v0.35.1@sha256:54dfef7b7b19c08c61e887aaba7704f34be3f7072d70dfc29cabe8548c4c9191
  • Repository scan for “v0.35.0” (excluding CHANGELOGs and markdown) returned no matches
  • JSON appVersion fields checked — none remained on v0.35.0

All clear for merge.

packages/system/cozystack-controller/values.yaml (1)

2-2: Controller image and cozystackVersion updated to v0.35.1 — consistent

Image digest and version string are aligned with the release. No further changes needed here.

Also applies to: 5-5

packages/apps/http-cache/images/nginx-cache.tag (1)

1-1: Nginx-cache digest updated

Digest-only refresh while keeping version 0.7.0 is fine for reproducibility. No issues spotted.

packages/system/dashboard/values.yaml (1)

22-22: Verification complete: all image tags updated to v0.35.1

  • No instances of v0.35.0 found in dashboard or kubeapps-apis image tags or references.
  • dashboard tag bumped to v0.35.1 (digest unchanged).
  • kubeapps-apis tag and digest updated to v0.35.1.

Approving these changes.

packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml (1)

79-79: appVersion in Dashboard config updated to v0.35.1 — aligned with values

JSON config now matches the rest of the release metadata.

packages/core/testing/values.yaml (1)

2-2: E2E sandbox image bump looks consistent and pinned — LGTM

  • Tag updated to v0.35.1 with the expected sha256 digest.
  • No lingering v0.35.0 references found in the repo.
  • Unable to auto-verify the digest against GHCR (registry requires auth); please manually confirm that
    sha256:680783a2394abdd74faae38e9c91c51b5660b641fa4adf0535038bbd50845331
    matches ghcr.io/cozystack/cozystack/e2e-sandbox:v0.35.1.
packages/system/kubeovn-webhook/values.yaml (1)

3-3: Kube-OVN webhook image bump and digest pinning — manual digest verification required

The automated registry HEAD request didn’t return a digest (GHCR enforces authentication), so please confirm that the pinned digest in packages/system/kubeovn-webhook/values.yaml matches the v0.35.1 image:

docker pull ghcr.io/cozystack/cozystack/kubeovn-webhook:v0.35.1
docker inspect --format='{{index .RepoDigests 0}}' ghcr.io/cozystack/cozystack/kubeovn-webhook:v0.35.1

• File: packages/system/kubeovn-webhook/values.yaml
Line 3:
image: ghcr.io/cozystack/cozystack/kubeovn-webhook:v0.35.1@sha256:095e979bcbaa275fd5ced339cd8f415b87dd151135735e37568c751da120137e

If the returned digest matches sha256:095e979bcbaa275fd5ced339cd8f415b87dd151135735e37568c751da120137e, you’re all set. Otherwise, update the digest in this values file.

packages/system/cozystack-api/values.yaml (1)

2-2: Cozystack API image updated to v0.35.1 and digest pinned — LGTM
The image tag and digest align with the v0.35.1 release; immutable digest pinning is retained.

Due to GHCR’s API requiring authenticated requests, the automated manifest fetch failed. Please manually confirm the checksum:

  • Pull and inspect the image digest:
    docker pull ghcr.io/cozystack/cozystack/cozystack-api:v0.35.1
    docker inspect --format='{{index .RepoDigests 0}}' ghcr.io/cozystack/cozystack/cozystack-api:v0.35.1

packages/system/cozystack-api/values.yaml (line 2):

  image: ghcr.io/cozystack/cozystack/cozystack-api:v0.35.1@sha256:84d9fcccb4bb9bdb72110184106e03d7ba9f7ecd4e3bd1a5a584933886173799
packages/system/kamaji/values.yaml (1)

6-6: Both Kamaji controller and migrate-image digests verified
All image references in packages/system/kamaji/values.yaml point to ghcr.io/cozystack/cozystack/kamaji:v0.35.1@sha256:1413443f96118acd72bd4a1bf5a809394133a7e155fac49e91979a47add7abd7, and a GHCR manifest lookup confirms the digest matches. LGTM.

packages/system/kubeovn/values.yaml (1)

67-67: Kube-OVN image digest refreshed while retaining v1.13.14 tag — LGTM

Only the sha256 digest changed for the same upstream version, preserving version intent while ensuring immutability.

Unable to fetch the digest for ghcr.io/cozystack/cozystack/kubeovn:v1.13.14 programmatically. Please manually confirm—via the GHCR UI or by fetching the manifest—that the pinned digest
sha256:6d3e1fecff095846d4bdc32a72d24077199f5cb202a300c82b78032fd6e5c302
matches before merging.

packages/extra/bootbox/images/matchbox.tag (1)

1-1: Image bump to v0.35.1 verified — no old references remain
Tag and digest are pinned; a repository-wide scan found no lingering v0.35.0 references. All good.

packages/system/objectstorage-controller/values.yaml (1)

3-3: Approve objectstorage-controller v0.35.1 bump; no old references found

Controller image updated to v0.35.1 with digest pinning. Verified no remaining v0.35.0 references. Looks good.

packages/extra/seaweedfs/images/objectstorage-sidecar.tag (1)

1-1: ✅ Sidecar image bump to v0.35.1 verified
Tag file and seaweedfs cosi.sidecar.image in values.yaml match exactly, and there are no remaining references to v0.35.0.
Approving code changes.

packages/system/seaweedfs/values.yaml (1)

119-119: COSI sidecar image updated to v0.35.1; matches digest pinning strategy

Update aligns with the tag file and broader release. Looks good.

You can re-run the consistency check from the sidecar tag file comment to ensure this value matches the tag file and that no v0.35.0 references remain.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release-0.35.1

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

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 automates the preparation for the v0.35.1 release by updating version strings and container image digests across various configuration files for different components of the Cozystack system. The changes ensure that all referenced images and internal version indicators align with the new release.

Highlights

  • Image and Component Version Updates: Updated version tags and SHA256 digests for numerous container images across different Cozystack components, including nginx-cache, installer, e2e-sandbox, matchbox, objectstorage-sidecar, cozystack-api, cozystack-controller, dashboard, kubeapps-apis, kamaji, kubeovn-webhook, kubeovn, and objectstorage-controller.
  • Specific Version String Increments: The cozystackVersion in the cozystack-controller configuration and the appVersion in the dashboard configmap were specifically incremented to v0.35.1.
  • Configuration File Updates: The changes primarily involve updating image references in .tag files and values.yaml configuration files to point to the new v0.35.1 release artifacts, ensuring all components align with the new release.
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

  1. 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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request prepares for the v0.35.1 release by updating version numbers and image digests across various configuration files. The changes are mostly straightforward version bumps. However, I've identified two instances where image tags were updated but their corresponding digests were not, which could lead to deploying incorrect image versions. Please review the comments for details.

@@ -19,7 +19,7 @@ kubeapps:
image:
registry: ghcr.io/cozystack/cozystack
repository: dashboard
tag: v0.35.0
tag: v0.35.1

Choose a reason for hiding this comment

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

high

The image tag has been updated to v0.35.1, but the corresponding digest on the next line appears to be unchanged from the previous version. This is inconsistent. If a new image was built for this release, the digest should also be updated to ensure the correct image is deployed.

@@ -1,3 +1,3 @@
objectstorage:
controller:
image: "ghcr.io/cozystack/cozystack/objectstorage-controller:v0.35.0@sha256:7b8e50fd0912155dec48919c18ad6ee4601720d8e31ee8367464b53c9f98f681"
image: "ghcr.io/cozystack/cozystack/objectstorage-controller:v0.35.1@sha256:7b8e50fd0912155dec48919c18ad6ee4601720d8e31ee8367464b53c9f98f681"

Choose a reason for hiding this comment

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

high

The image tag was updated to v0.35.1, but the SHA256 digest remains the same as the one for v0.35.0. This is likely an error and will result in deploying an older image. Please update the digest to match the new image.

@kvaps kvaps merged commit 60965df into main Aug 19, 2025
20 checks passed
@kvaps kvaps deleted the release-0.35.1 branch August 19, 2025 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Releasing a new Cozystack version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants