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

chore: bump greptimedb version to v0.11.2 #217

Merged

Conversation

daviderli614
Copy link
Member

@daviderli614 daviderli614 commented Jan 4, 2025

Summary by CodeRabbit

  • New Features

    • No new user-facing features introduced
  • Bug Fixes

    • No specific bug fixes mentioned
  • Chores

    • Updated GreptimeDB Helm charts for cluster and standalone deployments
    • Upgraded application version from v0.11.1 to v0.11.2
    • Updated Helm chart versions for cluster (0.2.42 → 0.2.43) and standalone (0.1.38 → 0.1.39)

Copy link
Contributor

coderabbitai bot commented Jan 4, 2025

Walkthrough

This pull request updates the Helm charts for both GreptimeDB cluster and standalone deployments. The changes are consistent across multiple files, incrementing version numbers and image tags from v0.11.1 to v0.11.2. The modifications include updates to Chart.yaml, README.md, and values.yaml files for both deployment types, ensuring version alignment across the Helm chart configurations.

Changes

File Change Summary
charts/greptimedb-cluster/Chart.yaml Version bumped from 0.2.42 to 0.2.43, AppVersion updated from 0.11.1 to 0.11.2
charts/greptimedb-cluster/README.md Version and image tag updated to match chart version
charts/greptimedb-cluster/values.yaml Image tag updated from v0.11.1 to v0.11.2
charts/greptimedb-standalone/Chart.yaml Version bumped from 0.1.38 to 0.1.39, AppVersion updated from 0.11.1 to 0.11.2
charts/greptimedb-standalone/README.md Version and image tag updated to match chart version
charts/greptimedb-standalone/values.yaml Image tag updated from v0.11.1 to v0.11.2

Poem

🐰 Hop, hop, version update time!
Charts aligned, everything's fine
From 0.11.1 to 0.11.2 we climb
GreptimeDB's charts now sparkle and shine
A rabbit's version dance, so sublime! 🚀


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1564591 and 50e9a98.

📒 Files selected for processing (6)
  • charts/greptimedb-cluster/Chart.yaml (1 hunks)
  • charts/greptimedb-cluster/README.md (2 hunks)
  • charts/greptimedb-cluster/values.yaml (1 hunks)
  • charts/greptimedb-standalone/Chart.yaml (1 hunks)
  • charts/greptimedb-standalone/README.md (2 hunks)
  • charts/greptimedb-standalone/values.yaml (1 hunks)
✅ Files skipped from review due to trivial changes (4)
  • charts/greptimedb-standalone/Chart.yaml
  • charts/greptimedb-standalone/README.md
  • charts/greptimedb-cluster/Chart.yaml
  • charts/greptimedb-cluster/README.md
🔇 Additional comments (2)
charts/greptimedb-standalone/values.yaml (1)

7-7: Version update looks good!

The image tag has been correctly updated to v0.11.2 for the standalone deployment.

Let's verify version consistency across related files:

✅ Verification successful

Version consistency verified across standalone deployment files

The version 0.11.2 is consistently referenced across all relevant files in the charts/greptimedb-standalone directory:

  • values.yaml: Image tag set to v0.11.2
  • Chart.yaml: AppVersion set to 0.11.2
  • README.md: Both AppVersion badge and values table show 0.11.2
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across standalone deployment files
echo "Checking version references in standalone deployment files..."
rg "0\.11\.[12]" charts/greptimedb-standalone/

Length of output: 727

charts/greptimedb-cluster/values.yaml (1)

7-7: Version update looks good!

The image tag has been correctly updated to v0.11.2 for the cluster deployment.

Let's verify version consistency across related files:

✅ Verification successful

Version consistency verified across cluster deployment files

The version 0.11.2 is consistently referenced across all relevant files in the greptimedb-cluster chart:

  • values.yaml: image.tag set to "v0.11.2"
  • Chart.yaml: appVersion set to 0.11.2
  • README.md: AppVersion badge and values table showing 0.11.2
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across cluster deployment files
echo "Checking version references in cluster deployment files..."
rg "0\.11\.[12]" charts/greptimedb-cluster/

Length of output: 706


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>, please review it.
    • 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 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 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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

@killme2008 killme2008 left a comment

Choose a reason for hiding this comment

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

LGTM

@killme2008 killme2008 merged commit 03ebef0 into GreptimeTeam:main Jan 4, 2025
3 checks passed
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.

2 participants