Repository navigation
chore: update GreptimeDB to v1.2.0 - #140
Merged
Merged
Conversation
Signed-off-by: discord9 <discord9@163.com>
killme2008
approved these changes
Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Update the shared
greptimedb-common.ymlimage fromdocker.io/greptime/greptimedb:v1.1.4tov1.2.0, using.github/scripts/release-patch.sh 1.2.0. No demo configuration or commands are otherwise changed.Verification
git diff --check: passed.docker compose -f <entrypoint> config --quiet: passed for all 15 compose entrypoints importing the shared file. Unset demo-specific environment variables produced warnings, not validation failures.--rpc-addrargument remains a supported alias in the published v1.2.0 source.Release state
Manually prepares the downstream update skipped by the release workflow. The v1.2.0 artifacts are published and verified; GitHub still marks v1.2.0 as Pre-release. This PR does not promote the GitHub release or merge/deploy anything.
Release: https://github.com/GreptimeTeam/greptimedb/releases/tag/v1.2.0
Release tracking: GreptimeTeam/greptimedb#9015