chore: bump version rc.2

[WenyXu]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

as title

PR Checklist

Please convert it to a draft if some of the following conditions are not met.

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR requires documentation updates.
• API changes are backward compatible.
• Schema or data changes are backward compatible.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on advancing the project's release cycle by incrementing the release candidate version across its various components. This ensures that all internal packages and the main workspace are aligned with the 1.0.0-rc.2 designation, preparing the codebase for subsequent development and testing phases.

Highlights

• Version Bump: The release candidate version for the entire workspace and numerous internal packages has been updated from 1.0.0-rc.1 to 1.0.0-rc.2.
• Dependency Lock File Update: The Cargo.lock file was updated to reflect the new 1.0.0-rc.2 version for all affected internal dependencies, ensuring consistent builds.

Changelog

• Cargo.lock
  • Updated 'api' package version to '1.0.0-rc.2'
  • Updated 'auth' package version to '1.0.0-rc.2'
  • Updated 'cache' package version to '1.0.0-rc.2'
  • Updated 'catalog' package version to '1.0.0-rc.2'
  • Updated 'cli' package version to '1.0.0-rc.2'
  • Updated 'client' package version to '1.0.0-rc.2'
  • Updated 'substrait' dependency version to '1.0.0-rc.2' for 'client'
  • Updated 'cmd' package version to '1.0.0-rc.2'
  • Updated 'common-base' package version to '1.0.0-rc.2'
  • Updated 'common-catalog' package version to '1.0.0-rc.2'
  • Updated 'common-config' package version to '1.0.0-rc.2'
  • Updated 'common-datasource' package version to '1.0.0-rc.2'
  • Updated 'common-decimal' package version to '1.0.0-rc.2'
  • Updated 'common-error' package version to '1.0.0-rc.2'
  • Updated 'common-event-recorder' package version to '1.0.0-rc.2'
  • Updated 'common-frontend' package version to '1.0.0-rc.2'
  • Updated 'common-function' package version to '1.0.0-rc.2'
  • Updated 'common-greptimedb-telemetry' package version to '1.0.0-rc.2'
  • Updated 'common-grpc' package version to '1.0.0-rc.2'
  • Updated 'common-grpc-expr' package version to '1.0.0-rc.2'
  • Updated 'common-macro' package version to '1.0.0-rc.2'
  • Updated 'common-mem-prof' package version to '1.0.0-rc.2'
  • Updated 'common-memory-manager' package version to '1.0.0-rc.2'
  • Updated 'common-meta' package version to '1.0.0-rc.2'
  • Updated 'common-options' package version to '1.0.0-rc.2'
  • Updated 'common-plugins' package version to '1.0.0-rc.2'
  • Updated 'common-pprof' package version to '1.0.0-rc.2'
  • Updated 'common-procedure' package version to '1.0.0-rc.2'
  • Updated 'common-procedure-test' package version to '1.0.0-rc.2'
  • Updated 'common-query' package version to '1.0.0-rc.2'
  • Updated 'common-recordbatch' package version to '1.0.0-rc.2'
  • Updated 'common-runtime' package version to '1.0.0-rc.2'
  • Updated 'common-session' package version to '1.0.0-rc.2'
  • Updated 'common-sql' package version to '1.0.0-rc.2'
  • Updated 'common-stat' package version to '1.0.0-rc.2'
  • Updated 'common-telemetry' package version to '1.0.0-rc.2'
  • Updated 'common-test-util' package version to '1.0.0-rc.2'
  • Updated 'common-time' package version to '1.0.0-rc.2'
  • Updated 'common-version' package version to '1.0.0-rc.2'
  • Updated 'common-wal' package version to '1.0.0-rc.2'
  • Updated 'common-workload' package version to '1.0.0-rc.2'
  • Updated 'datanode' package version to '1.0.0-rc.2'
  • Updated 'datatypes' package version to '1.0.0-rc.2'
  • Updated 'file-engine' package version to '1.0.0-rc.2'
  • Updated 'flow' package version to '1.0.0-rc.2'
  • Updated 'substrait' dependency version to '1.0.0-rc.2' for 'flow'
  • Updated 'frontend' package version to '1.0.0-rc.2'
  • Updated 'index' package version to '1.0.0-rc.2'
  • Updated 'log-query' package version to '1.0.0-rc.2'
  • Updated 'log-store' package version to '1.0.0-rc.2'
  • Updated 'meta-client' package version to '1.0.0-rc.2'
  • Updated 'meta-srv' package version to '1.0.0-rc.2'
  • Updated 'metric-engine' package version to '1.0.0-rc.2'
  • Updated 'mito-codec' package version to '1.0.0-rc.2'
  • Updated 'mito2' package version to '1.0.0-rc.2'
  • Updated 'object-store' package version to '1.0.0-rc.2'
  • Updated 'operator' package version to '1.0.0-rc.2'
  • Updated 'substrait' dependency version to '1.0.0-rc.2' for 'operator'
  • Updated 'partition' package version to '1.0.0-rc.2'
  • Updated 'pipeline' package version to '1.0.0-rc.2'
  • Updated 'plugins' package version to '1.0.0-rc.2'
  • Updated 'promql' package version to '1.0.0-rc.2'
  • Updated 'puffin' package version to '1.0.0-rc.2'
  • Updated 'query' package version to '1.0.0-rc.2'
  • Updated 'substrait' dependency version to '1.0.0-rc.2' for 'query'
  • Updated 'servers' package version to '1.0.0-rc.2'
  • Updated 'session' package version to '1.0.0-rc.2'
  • Updated 'sql' package version to '1.0.0-rc.2'
  • Updated 'sqlness-runner' package version to '1.0.0-rc.2'
  • Updated 'standalone' package version to '1.0.0-rc.2'
  • Updated 'store-api' package version to '1.0.0-rc.2'
  • Updated 'substrait' package version to '1.0.0-rc.2'
  • Updated 'table' package version to '1.0.0-rc.2'
  • Updated 'tests-fuzz' package version to '1.0.0-rc.2'
  • Updated 'tests-integration' package version to '1.0.0-rc.2'
  • Updated 'substrait' dependency version to '1.0.0-rc.2' for 'tests-integration'
• Cargo.toml
  • Updated the workspace package version to '1.0.0-rc.2'.

Activity

• The pull request was created by WenyXu with the intention to bump the version to 1.0.0-rc.2 as indicated by the title and description.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request bumps the workspace version from 1.0.0-rc.1 to 1.0.0-rc.2. The changes correctly update the version in Cargo.toml and propagate this change to the Cargo.lock file for all workspace members. The changes are consistent with the goal of preparing for a new release candidate and appear to be correct.

_{Note: Security Review has been skipped due to the limited scope of the PR.}