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.0 #212

Merged

Conversation

daviderli614
Copy link
Member

@daviderli614 daviderli614 commented Dec 10, 2024

Summary by CodeRabbit

  • New Features

    • Updated versions for the greptimedb-cluster and greptimedb-standalone Helm charts to 0.2.40 and 0.1.36, respectively.
    • Updated application version to 0.11.0 for both clusters.
    • Updated Docker image tags to v0.11.0 for GreptimeDB in both clusters.
  • Documentation

    • Revised README files to reflect new version numbers and image tags for both Helm charts.

Copy link
Contributor

coderabbitai bot commented Dec 10, 2024

Walkthrough

The pull request involves updates to the Helm charts for the greptimedb-cluster and greptimedb-standalone. The Chart.yaml, README.md, and values.yaml files for both charts have been modified to reflect new versioning information. Specifically, the version and appVersion have been incremented, and the image tag for the GreptimeDB has been updated to a newer version. No structural changes were made to the files, and the content remains largely the same.

Changes

File Path Change Summary
charts/greptimedb-cluster/Chart.yaml Updated version from 0.2.39 to 0.2.40, appVersion from 0.10.2 to 0.11.0.
charts/greptimedb-cluster/README.md Updated version badge from 0.2.39 to 0.2.40, app version from 0.10.2 to 0.11.0, and image tag from v0.10.2 to v0.11.0.
charts/greptimedb-cluster/values.yaml Updated image tag from v0.10.2 to v0.11.0.
charts/greptimedb-standalone/Chart.yaml Updated version from 0.1.35 to 0.1.36, appVersion from 0.10.2 to 0.11.0.
charts/greptimedb-standalone/README.md Updated version badge from 0.1.35 to 0.1.36, app version from 0.10.2 to 0.11.0, and image tag from v0.10.2 to v0.11.0.
charts/greptimedb-standalone/values.yaml Updated image tag from v0.10.2 to v0.11.0.

Possibly related PRs

Suggested reviewers

  • killme2008

Poem

In the fields where data hops,
Versions change, and never stops.
From 0.10.2 to 0.11.0,
Our charts now shine, a brighter glow!
With every tag, we leap and bound,
In the world of code, joy is found! 🐰✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ac3a743 and c82df8a.

📒 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 (3)
  • charts/greptimedb-standalone/Chart.yaml
  • charts/greptimedb-cluster/Chart.yaml
  • charts/greptimedb-standalone/README.md
🔇 Additional comments (4)
charts/greptimedb-cluster/README.md (1)

5-5: Version updates look good!

The version badges have been correctly updated:

  • Version: 0.2.40
  • AppVersion: 0.11.0

These changes align with the PR objective to bump the greptimedb version.

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

7-7: Image tag update is correct!

The greptimedb image tag has been properly updated to v0.11.0, which is consistent with the version bump in the README.md file.


7-7: Verify version consistency across the repository

Let's ensure all version references have been updated consistently.

✅ Verification successful

Version references are consistent across the repository

The version references are consistent across the repository:

  • Chart.yaml: appVersion: 0.11.0
  • values.yaml: tag: v0.11.0
  • No references to old version 0.10.2 were found in yaml or markdown files
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any remaining references to the old version
# This helps ensure we haven't missed any version updates

echo "Checking for any remaining references to v0.10.2..."
rg "0\.10\.2|v0\.10\.2" --type yaml --type md

echo "Checking Chart.yaml for version consistency..."
cat charts/greptimedb-cluster/Chart.yaml

Length of output: 1362

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

7-7: Verify version consistency across Helm charts

The image tag update to v0.11.0 aligns with the PR objective. However, let's ensure version consistency across all related files.

✅ Verification successful

Version consistency verified across Helm charts and Docker image

The version update to v0.11.0 is consistent across:

  • Both standalone and cluster Chart.yaml files (appVersion: 0.11.0)
  • Both values.yaml files use tag: "v0.11.0" for the main GreptimeDB image
  • The tag exists in Docker Hub
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

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

echo "Checking version consistency in Chart.yaml files..."
for chart in greptimedb-standalone greptimedb-cluster; do
  if [ -f "charts/${chart}/Chart.yaml" ]; then
    echo "=== ${chart} Chart.yaml ==="
    grep -E "version:|appVersion:" "charts/${chart}/Chart.yaml"
  fi
done

echo -e "\nChecking image tag in values.yaml files..."
for chart in greptimedb-standalone greptimedb-cluster; do
  if [ -f "charts/${chart}/values.yaml" ]; then
    echo "=== ${chart} values.yaml ==="
    grep -A 1 "tag:" "charts/${chart}/values.yaml"
  fi
done

# Check if v0.11.0 exists in the greptime/greptimedb Docker Hub repository
echo -e "\nVerifying v0.11.0 tag exists in Docker Hub..."
curl -s "https://hub.docker.com/v2/repositories/greptime/greptimedb/tags/?page_size=100" | jq -r '.results[] | select(.name=="v0.11.0") | .name'

Length of output: 1849


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. (Experiment)
  • @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.

@daviderli614 daviderli614 merged commit ff90aff into GreptimeTeam:main Dec 10, 2024
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