Skip to content

Prepare chdb-java 1.1.0 after verified Central snapshot - #47

Merged
ShawnChen-Sirius merged 1 commit into
mainfrom
codex/release-v1-1-0
Nov 18, 2026
Merged

ShawnChen-Sirius merged 1 commit into
mainfrom
codex/release-v1-1-0

Conversation

@ShawnChen-Sirius

@ShawnChen-Sirius ShawnChen-Sirius commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Set all 10 reactor POMs to 1.1.0. Keep chDB Core 26.11.1, JNI ABI 5, Java API version 1, and the six-module Central publishing plan unchanged.
  • Record the successful Central snapshot deployment and independent artifact-consumption evidence in docs/release-readiness.md.
  • Explicitly retain outstanding release gates; this preparation does not claim that stable 1.1.0 is published or approved.

Completed snapshot evidence

  • PR Fix CI publishing with a verified Maven toolchain #46 merged at 7cb8f73; build run 44403289591 passed all 14 jobs.
  • Real snapshot release run 44405871446 succeeded on that same commit, including all four staging jobs and unified deployment.
  • Independently downloaded all six modules from Central snapshots, verified all 24 POM/main-JAR/sources/javadoc signatures against fingerprint 313B34913A0E8153DE70C9222314498A0D48461B, and checked all four native manifests against the expected commit and engine.
  • Separate Maven cache and credential-free settings on Java 11/macOS ARM64: JDBC returned engine=26.11.1 rows=1000 sum=499500; Arrow returned 42. JDBC-only dependencies contained no Arrow.
  • The earlier HTTP 502 did not recur, but its original server-side cause remains unconfirmed.

Validation of this version change

  • All 12 release-tooling regression tests passed.
  • Java 11: 178 JDBC unit tests and 1 Arrow unit test passed; 29 native Arrow tests were skipped in this unit-only run.
  • All six generated 1.1.0 consumer POMs passed the standalone POM validator.
  • git diff --check passed.
  • Build run 44410639227 is in progress for head 3988650.

Outstanding before a stable tag / upload

  • Written engine-redistribution decision required by the release checklist.
  • Two independent external-project validation reports and a current-engine concurrent soak, or explicit release-owner decisions about those gates. The temporary technical consumer checks and historical old-engine soak do not discharge them.
  • v* tag protection against update and deletion; only the branch ruleset Need PR was found at the last check.
  • Fresh Usage Center check in the ClickHouse Central workspace; the browser is signed out, so the previous 888/1000 observation is not current.
  • Final release notes and stable installation documentation, followed by successful four-platform build CI for the exact merged release commit.

The release owner already waived the one-week RC waiting window and deferred required environment reviewers/admin-bypass settings for this release. No additional gate is waived here.

Safety

Creating or merging this PR does not itself trigger Central publication. A separately confirmed matching v1.1.0 tag is required; autoPublish=false keeps the resulting stable bundle pending explicit Portal publication. Pushes, tag creation on the remote, uploads and Portal Publish remain separately confirmed operations.

Note

Bump chdb-java from 1.1.0-SNAPSHOT to 1.1.0 for stable release prep

Changes the version in all module pom.xml files (root, chdb-arrow, chdb-bom, chdb-jdbc, chdb-native-*, chdb-examples, chdb-integration-tests) from 1.1.0-SNAPSHOT to 1.1.0.

Adds a stable-release checkpoint dated 2026-11-19 to release-readiness.md. It records build, Central snapshot, signature, and platform checks, and lists remaining steps: engine-redistribution decision, release-gate decisions, tag protection, quota check, release docs, and release-commit CI. The version change itself does not tag, upload, or publish the release.

Risk: check any dependency on the 1.1.0-SNAPSHOT coordinates; builds now resolve 1.1.0.

Macroscope summarized 3988650.

@ShawnChen-Sirius
ShawnChen-Sirius merged commit 30e3bd5 into main Nov 18, 2026
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant