From a3b02b8e6a1479250c3622104d2fc171ffd9a8df Mon Sep 17 00:00:00 2001 From: Shawn Chen Date: Tue, 17 Nov 2026 11:01:08 +1300 Subject: [PATCH] Keep v1.1.0 RC tags off the Central release path --- .github/workflows/release.yml | 3 +++ README.md | 4 ++-- docs/publishing.md | 31 ++++++++++++++++++------------- 3 files changed, 23 insertions(+), 15 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 79747cf..743faa3 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -64,6 +64,9 @@ on: # succeeded for this exact commit rather than assuming a tag implies a tested tree. tags: - "v*" + # RC tags are handled by rc-release.yml and staged for maven.chdb.io. Without this + # exclusion they also start the Central workflow, which fails on the SNAPSHOT POM. + - "!v*-rc.*" # Never a preview: `v1.0.0-preview.1` matches `v*` and preflight would accept it, so # the Central path would stage, sign and offer a preview in the portal, where a release # cannot be unpublished. preview-release.yml publishes those. diff --git a/README.md b/README.md index 15b4e48..14bb5ff 100644 --- a/README.md +++ b/README.md @@ -7,8 +7,8 @@ streaming, forward-only result sets over ClickHouse SQL. > **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. This development branch targets stable core `26.11.1` and adds an -> optional `chdb-arrow` module for the planned `v1.1.0` stable release; those artifacts have not -> been published. See the +> optional `chdb-arrow` module for the proposed `v1.1.0-rc.1` validation release ahead of +> `v1.1.0` stable; those artifacts are not published yet. See the > [Arrow Java getting-started guide](chdb-arrow/README.md#getting-started) for examples > and [What works today](#what-works-today) for the JDBC release status. diff --git a/docs/publishing.md b/docs/publishing.md index 268030b..4e968d3 100644 --- a/docs/publishing.md +++ b/docs/publishing.md @@ -403,16 +403,21 @@ Each step can invalidate the next, so: --- -## 8. RCs on GitHub Packages - -The first test version is `1.0.0-rc.1`, released by pushing the tag `v1.0.0-rc.1`. The -`.github/workflows/rc-release.yml` workflow builds all four native packages on native runners -and publishes the parent POM, JDBC driver, platform packages and BOM to: - -```text -https://maven.pkg.github.com/chdb-io/chdb-java -``` - -Consumers configure that repository and a GitHub classic PAT with `read:packages`. Stable -versions keep the same coordinates and later move to Maven Central; no dependency coordinate -change is required. +## 8. RCs on maven.chdb.io + +`1.0.0-rc.1` and `1.0.0-rc.2` were earlier test versions. The next proposed test version is +`v1.1.0-rc.1`, before the planned `v1.1.0` stable release. The development POMs stay at +`1.1.0-SNAPSHOT`; `.github/workflows/rc-release.yml` derives `1.1.0-rc.1` from the tag and +sets it in the build workspace. The Central release workflow explicitly excludes `-rc.*` +tags, so the same tag cannot start both publication routes. + +The RC workflow builds on all four native runners, tests Arrow against each staged pair, +and produces a `maven-repository` artifact containing the parent POM, BOM, JDBC, optional +Arrow and all four platform packages. **A successful workflow does not publish them.** After +inspecting that artifact, use the [Vercel Maven gateway runbook](../deploy/vercel-maven/README.md) +to upload it manually. `scripts/publish-rc-repository.sh` checks all versioned paths before +upload and refuses to overwrite a previously published artifact. + +Consumers add `https://maven.chdb.io` as a Maven repository and specify the exact RC version; +no GitHub PAT is needed. This RC remains a pre-release and does not satisfy the stable release +gates in `docs/release-readiness.md`.