chore: bump greptimedb version to v0.9.5

[daviderli614]

Summary by CodeRabbit

• New Features

  • Updated Helm charts for greptimedb-cluster and greptimedb-standalone to version 0.2.21 and 0.1.24, respectively.
  • Application version updated to 0.9.5 for both clusters.
  • Main GreptimeDB image tag updated to v0.9.5.

• Documentation

  • README files updated to reflect new versioning information and image tags.

[coderabbitai]

Walkthrough

The pull request includes updates to the Helm charts for both the greptimedb-cluster and greptimedb-standalone. The Chart.yaml files for both charts have had their version numbers incremented, along with updates to the application version. The README.md files and values.yaml files for each chart have also been modified to reflect these version changes, specifically updating the image tags to the new application version.

Changes

File Path	Change Summary
charts/greptimedb-cluster/Chart.yaml	Updated version from 0.2.20 to 0.2.21 and appVersion from 0.9.4 to 0.9.5.
charts/greptimedb-cluster/README.md	Updated Version from 0.2.20 to 0.2.21, AppVersion from 0.9.4 to 0.9.5, and image tag from v0.9.4 to v0.9.5.
charts/greptimedb-cluster/values.yaml	Updated image tag from v0.9.4 to v0.9.5.
charts/greptimedb-standalone/Chart.yaml	Updated version from 0.1.23 to 0.1.24 and appVersion from 0.9.4 to 0.9.5.
charts/greptimedb-standalone/README.md	Updated Version from 0.1.23 to 0.1.24, AppVersion from 0.9.4 to 0.9.5, and image tag from v0.9.4 to v0.9.5.
charts/greptimedb-standalone/values.yaml	Updated image tag from v0.9.4 to v0.9.5.

Possibly related PRs

• chore: bump greptimedb version from v0.9.0 to v0.9.1 #151: Similar version updates in the greptimedb-cluster Helm chart files.
• chore: bump greptimedb version from v0.9.1 to v0.9.2 #158: Reflects version increments in the greptimedb-cluster files.
• chore: bump greptimedb version from v0.9.2 to v0.9.3 #164: Updates in greptimedb-cluster files indicating version changes.
• chore: bump greptimedb version from v0.9.3 to v0.9.4 #168: Version increment updates in the greptimedb-cluster files.
• chore: bump greptimedb-operator version to v0.1.1 and add operator service configs #170: Updates to Chart.yaml and README.md for the greptimedb-operator involving version increments.
• chore: bump operator version #173: Version increment updates in the greptimedb-cluster files.

Suggested reviewers

• zyy17

Poem

In the fields where data flows,
New versions sprout like springtime grows.
From 0.9.4 to 0.9.5,
The charts now dance, alive, alive!
With tags that gleam, oh what a sight,
Our GreptimeDB shines ever bright! 🐇✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between ead535f and 3aef93d.

📒 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-cluster/Chart.yaml
• charts/greptimedb-cluster/README.md
• charts/greptimedb-standalone/Chart.yaml
• charts/greptimedb-standalone/README.md

🧰 Additional context used

🔇 Additional comments (1)

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

7-7: LGTM: Version bump looks good.

The update of the GreptimeDB image tag from v0.9.4 to v0.9.5 is correct and aligns with the PR objectives.

To ensure consistency across the chart, please run the following script to check if the version has been updated in all relevant files:

✅ Verification successful

: Version bump successfully verified.

The GreptimeDB image tag has been correctly updated to v0.9.5, and no unintended changes were found in other tags.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across chart files

# Check Chart.yaml
echo "Checking Chart.yaml:"
grep -n 'version:\|appVersion:' charts/greptimedb-cluster/Chart.yaml

# Check README.md
echo -e "\nChecking README.md:"
grep -n 'v0.9.5' charts/greptimedb-cluster/README.md

# Check values.yaml
echo -e "\nChecking values.yaml:"
grep -n 'tag:' charts/greptimedb-cluster/values.yaml

Length of output: 531

---

Script:

#!/bin/bash
# Description: Identify which 'tag:' corresponds to the GreptimeDB image in values.yaml

# Search for 'image:' lines and capture their corresponding 'tag:' lines
rg -A1 'image:' charts/greptimedb-cluster/values.yaml | grep 'tag:'

Length of output: 65

---

Script:

#!/bin/bash
# Description: Identify the 'tag:' associated with the GreptimeDB image in values.yaml

# Search for lines containing 'greptimedb' and capture the next few lines to find 'tag:'
rg -A3 'greptimedb' charts/greptimedb-cluster/values.yaml | grep 'tag:'

Length of output: 99