Skip to content

Prepare standalone artifacts for Maven Central release - #45

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

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

Conversation

@ShawnChen-Sirius

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

Copy link
Copy Markdown
Collaborator

Summary

Prepare plan A for the first stable chdb-java release, 1.1.0, while keeping the development POMs at 1.1.0-SNAPSHOT until snapshot validation is complete.

  • Publish only six library coordinates to Central: JDBC, Arrow, and four platform-specific native modules. Generate standalone consumer POMs with flatten-maven-plugin; skip the internal parent and BOM. Preserve the legacy RC publishing route.
  • Add pre-upload consumer POM validation and seven regression tests. Update the isolated consumer test to prove that a single native dependency resolves JDBC and runs without a published parent or BOM, with Arrow remaining optional.
  • Pin central-publishing-maven-plugin to 0.12.0, use required checksums, and exercise the deploy lifecycle with skipUpload=true during workflow dry runs. Keep autoPublish=false for manual Central Portal publication.
  • Update installation examples, publishing documentation, and the release checklist.

Validation

  • Build workflow for 6e3de50: https://github.com/chdb-io/chdb-java/actions/runs/44247438465 — all jobs successful.
  • Four native platforms: integration tests on Java 11, 17, 21, and 25, plus isolated repository consumer checks, all successful in CI.
  • Local Java 11: 178 JDBC unit tests and all 30 Arrow tests, including 29 native integration tests, passed against the pinned 26.11.1 engine.
  • Seven Python consumer POM regression tests and all six generated release consumer POM checks passed.
  • Local macOS ARM64 file-repository consumption passed: transitive JDBC, native extraction checksums, query results, missing/wrong platform diagnostics, and optional Arrow reading.
  • Three-module snapshot signing dry run passed with an isolated disposable test key; all twelve signatures verified. Uploads were disabled and publication URLs were overridden to an unreachable localhost endpoint. This does not validate the configured production signing key or Central token.
  • Workflow structure validation with actionlint -shellcheck="", consumer script shellcheck, and git diff --check passed. The full actionlint shellcheck pass reports existing shell-style warnings.

Current operator configuration and release-owner decisions

These updates occurred after the initial dated checkpoint recorded in docs/release-readiness.md:

  • The maintainer now has repository admin access. The maven-central environment exists and lists all four expected secrets; deployment rules allow main and v* tags. Secret values have not been read or validated.
  • The public signing key was independently retrieved from the Ubuntu keyserver through HKP port 80 and its fingerprint matched. HKPS/HTTPS lookups returned No data/404 during verification, so end-to-end Central verification remains necessary.
  • The release owner explicitly waived the minimum one-week RC validation window for this 1.1.0 release.
  • The release owner explicitly chose to defer required environment reviewers and disabling administrator bypass for this release. No environment protection settings were changed by this PR.
  • These decisions do not waive concurrent soak, licence/redistribution confirmation, independent external-consumer evidence, quota checks, or the remaining release gates.

Next steps — not performed by this PR

  1. Review and merge this preparation change.
  2. Run the four-platform snapshot dry run from main using the configured signing key.
  3. Separately authorize a real Central snapshot upload and verify fresh external consumption.
  4. Resolve the remaining release gates and tag protections before preparing the 1.1.0 release commit and matching tag.
  5. Upload and validate the stable bundle, inspect it, and separately confirm Publish in Central Portal.

Creating this PR does not merge code, create a release tag, trigger the release workflow, upload a snapshot, or publish a stable release.

Note

Prepare standalone consumer POMs for Maven Central release

  • Root pom.xml now skips deploy by default; the six library modules opt in via maven.deploy.skip=false. Adds flatten-maven-plugin 1.7.3 in ossrh mode to generate standalone consumer POMs without parent, BOM, build, or repository elements, and upgrades central-publishing-maven-plugin to 0.12.0 with required checksums.
  • New check-consumer-poms.py validates the flattened POMs (coordinates, required metadata, no parent/build/repositories, no test-scoped deps, exactly one non-optional JDBC dependency for non-JDBC modules). It has unit tests in test_consumer_poms.py, which the CI Java unit-test job now runs.
  • The release workflow validates the six consumer POMs before deploy; dry runs now execute deploy with skipUpload instead of verify.
  • Consumer docs and verification scripts drop the BOM import in favor of a shared version property with explicit dependency versions.
  • Behavioral Change: internal reactor POMs and the BOM are no longer deployed or published; dry-run releases run the deploy goal rather than verify.

Macroscope summarized 6e3de50.

@ShawnChen-Sirius
ShawnChen-Sirius merged commit 7649ef3 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