Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare release v0.14.0 #333

Merged
merged 1 commit into from
Sep 4, 2024
Merged

Prepare release v0.14.0 #333

merged 1 commit into from
Sep 4, 2024

Conversation

kvaps
Copy link
Member

@kvaps kvaps commented Sep 4, 2024

Signed-off-by: Andrei Kvapil [email protected]

Summary by CodeRabbit

  • New Features

    • Upgraded various container images to version v0.14.0, enhancing application performance and potentially introducing new features and bug fixes.
  • Bug Fixes

    • Improved version tracking for packages by updating commit hashes, enhancing clarity and traceability.
  • Chores

    • Updated configuration files to reflect the new image versions for components, ensuring the latest updates are utilized across the application.

Copy link
Contributor

coderabbitai bot commented Sep 4, 2024

Warning

Rate limit exceeded

@kvaps has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 27 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between c15510c and 95690ee.

Walkthrough

The changes involve updates to various configuration files, primarily focusing on incrementing the image tags for multiple components from version v0.13.0 to v0.14.0. Additionally, specific commit hashes have been added for version tracking in the versions_map file. These modifications ensure that the system utilizes the latest versions of the respective containers and packages, reflecting improvements and updates across the board.

Changes

Files Change Summary
manifests/cozystack-installer.yaml, packages/core/installer/values.yaml, packages/core/testing/values.yaml, packages/system/dashboard/values.yaml, packages/system/kamaji/values.yaml Updated image tags from v0.13.0 to v0.14.0 for various components, along with SHA256 checksum changes where applicable.
packages/apps/versions_map Updated version entries for clickhouse and ferretdb to include specific commit hashes, enhancing version traceability.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant System
    participant ContainerRegistry

    User->>System: Request to deploy application
    System->>ContainerRegistry: Pull image v0.14.0
    ContainerRegistry-->>System: Provide image v0.14.0
    System->>User: Application deployed with updated image
Loading

Poem

🐰 In the meadow, changes bloom,
New versions chase away the gloom.
With tags that hop from old to new,
Fresh features dance, and bugs bid adieu!
Let's celebrate with a joyful cheer,
For brighter days are surely near! 🌼✨


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?

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>.
    • Generate unit testing code for this file.
    • 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. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

  • 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
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (2)
packages/apps/versions_map (2)

6-6: Provide a specific commit hash for version tracking.

Using HEAD as the commit hash is not ideal for version tracking. Please update this entry with a specific commit hash to enable precise version referencing, similar to the other entries in this file.


11-11: Provide a specific commit hash for version tracking.

Using HEAD as the commit hash is not ideal for version tracking. Please update this entry with a specific commit hash to enable precise version referencing, similar to the other entries in this file.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 93018c4 and c15510c.

Files selected for processing (6)
  • manifests/cozystack-installer.yaml (2 hunks)
  • packages/apps/versions_map (1 hunks)
  • packages/core/installer/values.yaml (1 hunks)
  • packages/core/testing/values.yaml (1 hunks)
  • packages/system/dashboard/values.yaml (1 hunks)
  • packages/system/kamaji/values.yaml (1 hunks)
Files skipped from review due to trivial changes (2)
  • packages/core/installer/values.yaml
  • packages/system/dashboard/values.yaml
Additional comments not posted (6)
packages/core/testing/values.yaml (1)

2-2: LGTM!

The change updates the Docker image for end-to-end testing to version v0.14.0, aligning with the PR objective of preparing for the release. The addition of the specific commit hash ensures reproducibility and allows pinning to a specific version of the image.

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

6-6: LGTM!

The code change is approved.

packages/apps/versions_map (2)

5-5: LGTM!

The change is approved.


10-10: LGTM!

The change is approved.

manifests/cozystack-installer.yaml (2)

90-90: Verify the darkhttpd container image tag update.

Ensure that the v0.14.0 tag exists in the ghcr.io/aenix-io/cozystack/cozystack repository and contains the desired changes for this release.

Run the following script to verify the image tag:


71-71: Verify the cozystack container image tag update.

Ensure that the v0.14.0 tag exists in the ghcr.io/aenix-io/cozystack/cozystack repository and contains the desired changes for this release.

Run the following script to verify the image tag:

Signed-off-by: Andrei Kvapil <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant