Prepare release v0.21.1 #551
Conversation
dosubot
bot
added
the
size:M
|
Caution Review failedThe pull request is closed. WalkthroughThis pull request involves updating various container image versions and digests across multiple configuration files in the Cozystack project. The primary focus is on incrementing the Changes
Suggested labels
Suggested reviewers
Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (12)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (12)
manifests/cozystack-installer.yaml(2 hunks)packages/apps/http-cache/images/nginx-cache.tag(1 hunks)packages/apps/kubernetes/images/ubuntu-container-disk.tag(1 hunks)packages/apps/mysql/images/mariadb-backup.tag(1 hunks)packages/core/installer/values.yaml(1 hunks)packages/core/testing/values.yaml(1 hunks)packages/system/bucket/images/s3manager.tag(1 hunks)packages/system/cozystack-api/values.yaml(1 hunks)packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml(1 hunks)packages/system/dashboard/values.yaml(1 hunks)packages/system/kamaji/values.yaml(1 hunks)packages/system/kubeovn/values.yaml(1 hunks)
✅ Files skipped from review due to trivial changes (9)
- packages/core/testing/values.yaml
- packages/apps/http-cache/images/nginx-cache.tag
- packages/system/cozystack-api/values.yaml
- packages/apps/mysql/images/mariadb-backup.tag
- packages/core/installer/values.yaml
- packages/system/kamaji/values.yaml
- packages/system/kubeovn/values.yaml
- packages/system/bucket/images/s3manager.tag
- packages/apps/kubernetes/images/ubuntu-container-disk.tag
🔇 Additional comments (2)
packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml (1)
79-79: Dashboard appVersion matches container versions
The appVersion in the dashboard configuration has been correctly updated to v0.21.1, maintaining consistency with the container image versions.
packages/system/dashboard/values.yaml (1)
43-44: Image versions and digests updated consistently
Both components have been updated to v0.21.1 with their corresponding new digests:
- Dashboard: tag v0.21.1, digest sha256:fa9b6238da1dfaa15ec1c20c041103d6e07b5194cc54cf3cf4872f758ceaa085
- Kubeappsapis: tag v0.21.1, digest sha256:3ad47a120ae2bd83e1242430e17616a6500d627a7a6cef94095b9e6c1a9e85a8
Let's verify the image digests:
Also applies to: 49-50
| containers: | ||
| - name: cozystack | ||
| image: "ghcr.io/aenix-io/cozystack/cozystack:v0.21.0" | ||
| image: "ghcr.io/aenix-io/cozystack/cozystack:v0.21.1" |
There was a problem hiding this comment.
💡 Codebase verification
Container images are not accessible in the registry
The verification shows that:
- Both v0.21.1 images are not accessible
- Previous version (v0.21.0) images are also not accessible
- Unable to list tags for both repositories
This could mean either:
- The images haven't been published yet
- The repositories are private and require authentication
- The repository paths are incorrect
Please ensure that:
- The container images are published before merging this change
- The repository paths are correct
- If the repositories are private, proper authentication is configured in the deployment
🔗 Analysis chain
Version updates look consistent
Both container images have been updated to v0.21.1:
- cozystack container:
ghcr.io/aenix-io/cozystack/cozystack:v0.21.1 - darkhttpd container:
ghcr.io/aenix-io/cozystack/cozystack:v0.21.1
Let's verify the image availability:
Also applies to: 90-90
Container images v0.21.1 are not available in the registry
The verification shows that both container images are not accessible in the GitHub Container Registry:
ghcr.io/aenix-io/cozystack/cozystack:v0.21.1ghcr.io/aenix-io/cozystack/darkhttpd:v0.21.1
Let's verify if the previous version (v0.21.0) is available to ensure this isn't an authentication issue:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify that both images exist in the registry
# Note: This only checks if the images are accessible, not if they are properly signed
for image in "ghcr.io/aenix-io/cozystack/cozystack:v0.21.1" "ghcr.io/aenix-io/cozystack/darkhttpd:v0.21.1"; do
echo "Checking $image..."
curl -s -f -L -I "https://ghcr.io/v2/${image#ghcr.io/}/manifests/latest" || echo "Image not found: $image"
done
Length of output: 1319
Script:
#!/bin/bash
# Check if v0.21.0 images exist
for image in "ghcr.io/aenix-io/cozystack/cozystack:v0.21.0" "ghcr.io/aenix-io/cozystack/darkhttpd:v0.21.0"; do
echo "Checking $image..."
curl -s -f -L -I "https://ghcr.io/v2/${image#ghcr.io/}/manifests/latest" || echo "Image not found: $image"
done
# List available tags for these repositories
for repo in "aenix-io/cozystack/cozystack" "aenix-io/cozystack/darkhttpd"; do
echo -e "\nListing tags for $repo:"
curl -s -f -L "https://ghcr.io/v2/$repo/tags/list" || echo "Failed to list tags"
done
Length of output: 1934
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
force-pushed
the
release-v0.21.1
branch
from
4b7581b to
15b3e45
Compare
Signed-off-by: Andrei Kvapil kvapss@gmail.com
Summary by CodeRabbit