Skip to content

Point the README at 1.0.0-rc.2 #36

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.

Sign up for GitHub

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

Merged
wudidapaopao merged 1 commit into from
Nov 5, 2026
Merged

Point the README at 1.0.0-rc.2 #36

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand Down Expand Up @@ -57,7 +57,7 @@ on. The native package pulls in the driver, so declaring it alone is enough.
<dependency>
<groupId>com.clickhouse.chdb</groupId>
<artifactId>chdb-native-linux-x86_64-gnu</artifactId>
<version>1.0.0-rc.1</version>
<version>1.0.0-rc.2</version>
</dependency>
```

Expand All @@ -79,7 +79,7 @@ architecture — declare the driver plus each native package you need:
<dependency>
<groupId>com.clickhouse.chdb</groupId>
<artifactId>chdb-bom</artifactId>
<version>1.0.0-rc.1</version>
<version>1.0.0-rc.2</version>
<type>pom</type>
<scope>import</scope>
</dependency>
Expand Down
2 changes: 1 addition & 1 deletion docs/v1-progress.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion scripts/engine.properties
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.<n> versions may be cut (the next is 1.0.0-rc.2; 1.0.0-rc.1
# this is the baseline only -rc.<n> 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.
#
Expand Down
Loading