diff --git a/README.md b/README.md index f323d88..4836619 100644 --- a/README.md +++ b/README.md @@ -4,8 +4,8 @@ A JDBC driver for [chDB](https://github.com/chdb-io/chdb-core), the embedded bui ClickHouse. It runs the engine in your JVM's process — no server, no network — and gives you streaming, forward-only result sets over ClickHouse SQL. -> **Status: release candidate.** The first Maven release candidate is `v1.0.0-rc.1`, built with -> chDB Core `26.7.3`. RC artifacts are available from the public chDB Maven repository; the +> **Status: release candidate.** The current Maven release candidate is `v1.0.0-rc.2`, built with +> chDB Core `26.11.0-rc.2`. RC artifacts are available from the public chDB Maven repository; the > public API is not frozen. See > [What works today](#what-works-today). @@ -57,7 +57,7 @@ on. The native package pulls in the driver, so declaring it alone is enough. com.clickhouse.chdb chdb-native-linux-x86_64-gnu - 1.0.0-rc.1 + 1.0.0-rc.2 ``` @@ -79,7 +79,7 @@ architecture — declare the driver plus each native package you need: com.clickhouse.chdb chdb-bom - 1.0.0-rc.1 + 1.0.0-rc.2 pom import diff --git a/docs/v1-progress.md b/docs/v1-progress.md index f095b04..087c10b 100644 --- a/docs/v1-progress.md +++ b/docs/v1-progress.md @@ -33,7 +33,7 @@ versions can be cut while it is the baseline, and the stable release has to be p 6 on Linux x86_64. 26.11.0-rc.2 is the same baseline plus chdb-core #312, a pre-release too, so nothing about -§4.3 changes: the next cut from it is `1.0.0-rc.2`, `1.0.0-rc.1` stays on 26.7.3, and v26.11.1 +§4.3 changes: `1.0.0-rc.2` is cut from it, `1.0.0-rc.1` stays on 26.7.3, and v26.11.1 has to be pinned before `1.0.0`. The signal-handler fix holds on it too: `measure` reports zero and `stress` survives 6 of 6 on Linux x86_64. diff --git a/scripts/engine.properties b/scripts/engine.properties index b588792..8b11d37 100644 --- a/scripts/engine.properties +++ b/scripts/engine.properties @@ -21,7 +21,7 @@ # PyPI), pinned to validate the ClickHouse 26.11 baseline ahead of the stable v26.11.1. It is # v26.11.0-rc.1 plus chdb-core #312, on the same ClickHouse baseline (26.11.1.1). Work plan # section 4.3: a binding built on an engine RC is itself an RC and cannot be V1 GA, so while -# this is the baseline only -rc. versions may be cut (the next is 1.0.0-rc.2; 1.0.0-rc.1 +# this is the baseline only -rc. versions may be cut (1.0.0-rc.2 is cut from it; 1.0.0-rc.1 # stays on v26.7.3), and the stable engine has to be re-pinned before 1.0.0. The last stable # baseline was v26.7.3. #