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 version to v0.9.0 #4376

Merged
merged 2 commits into from
Jul 16, 2024
Merged

Conversation

evenyag
Copy link
Contributor

@evenyag evenyag commented Jul 16, 2024

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

#4364

What's changed and what's your intention?

Bump version to v0.9.0

Checklist

  • I have written the necessary rustdoc comments.
  • I have added the necessary unit tests and integration tests.
  • This PR requires documentation updates.

Summary by CodeRabbit

  • Chores
    • Updated project version to 0.9.0 in Cargo.toml.
    • Updated workflow configuration for the next release version to 0.10.0.

Copy link
Contributor

coderabbitai bot commented Jul 16, 2024

Walkthrough

This update involves incrementing the version numbers in both the GitHub Actions workflow and the Cargo.toml file. The scheduled release version is updated from v0.9.0 to v0.10.0 in the release.yml workflow, while the crate version in Cargo.toml has been updated from "0.8.2" to "0.9.0". These changes reflect an impending new release for the project.

Changes

File Change Summary
.github/workflows/release.yml Updated NEXT_RELEASE_VERSION from v0.9.0 to v0.10.0.
Cargo.toml Updated version from "0.8.2" to "0.9.0".

Poem

To the code we give a lift,
A version change, our little gift.
From 0.9 to 0.10 we go,
In Cargo.toml, progress shows.
A journey onward, code refined,
Another step for humankind. 🚀


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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

@github-actions github-actions bot added the docs-not-required This change does not impact docs. label Jul 16, 2024
@evenyag evenyag mentioned this pull request Jul 16, 2024
13 tasks
@evenyag evenyag marked this pull request as ready for review July 16, 2024 07:29
@evenyag evenyag requested a review from a team as a code owner July 16, 2024 07:29
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 (1)
Cargo.toml (1)

67-67: Updates to documentation and tests for version 0.9.0 are missing

The search did not find any references to the new version "0.9.0" in the rustdoc comments, unit tests, or integration tests. Ensure that these updates are made to maintain quality and compatibility.

  • Update rustdoc comments to reflect the new version.
  • Update unit tests and integration tests to include references to version "0.9.0".
Analysis chain

Version updated correctly to 0.9.0

The version number in the Cargo.toml file has been correctly updated from "0.8.2" to "0.9.0". This change aligns with the PR's objective to bump the version for the upcoming release.

However, as per the PR description, it's mentioned that rustdoc comments, unit tests, and integration tests related to this new version are pending. Ensure these are addressed to maintain quality and compatibility.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for updates in documentation and tests related to the new version.

# Test: Search for rustdoc comments, unit tests, and integration tests mentioning the new version 0.9.0.
rg --type rust -A 5 $'0\\.9\\.0'

Length of output: 31


Script:

#!/bin/bash
# Description: Check for any version numbers in rustdoc comments, unit tests, and integration tests.

# Test: Search for any version numbers in the rust files to verify if updates were made.
rg --type rust -A 5 '\d+\.\d+\.\d+'

Length of output: 103760

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between be3ea0f and b6ac823.

Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
Files selected for processing (2)
  • .github/workflows/release.yml (1 hunks)
  • Cargo.toml (1 hunks)
Files skipped from review due to trivial changes (1)
  • .github/workflows/release.yml

Copy link

codecov bot commented Jul 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.88%. Comparing base (7b28da2) to head (b6ac823).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4376      +/-   ##
==========================================
- Coverage   85.15%   84.88%   -0.27%     
==========================================
  Files        1074     1074              
  Lines      191836   191858      +22     
==========================================
- Hits       163364   162868     -496     
- Misses      28472    28990     +518     

@evenyag evenyag added this pull request to the merge queue Jul 16, 2024
Merged via the queue into GreptimeTeam:main with commit d6c7b84 Jul 16, 2024
59 of 70 checks passed
@evenyag evenyag deleted the chore/bump-v0.9 branch July 16, 2024 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-not-required This change does not impact docs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants