Skip to content

Keep v1.1.0 RC tags off the Central release path - #43

Merged
ShawnChen-Sirius merged 1 commit into
mainfrom
codex/v1-1-0-rc1-prep
Nov 16, 2026
Merged

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

Conversation

@ShawnChen-Sirius

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

Copy link
Copy Markdown
Collaborator

Summary

  • Exclude v*-rc.* tags from the Central release workflow. The existing RC workflow alone should build and stage v1.1.0-rc.1 for maven.chdb.io; a single tag must not start both routes.
  • Document the current RC path: four native packages, JDBC, optional Arrow, BOM and parent POM are staged as a maven-repository workflow artifact. A successful workflow does not upload anything; the inspected artifact is uploaded manually through the immutable-path Vercel Blob publisher.
  • Clarify that v1.1.0-rc.1 is a validation pre-release before the planned v1.1.0 stable version. Consumers must configure maven.chdb.io and request the explicit RC version.

Verification

  • actionlint validated release.yml and rc-release.yml; git diff --check passed.
  • The branch retains 1.1.0-SNAPSHOT POMs. The RC workflow derives 1.1.0-rc.1 in its build workspace from the tag.

No tag, Maven repository upload, GitHub Release or Central publication is performed by this PR. Merge and verify branch/main CI before requesting a separate confirmed v1.1.0-rc.1 tag push.

Note

Exclude v*-rc.* tags from the Central release workflow

Adds a negative tag pattern to the push-tag trigger in release.yml so RC tags skip the Central release workflow. RC tags are handled by rc-release.yml; running the Central workflow on them would publish SNAPSHOT POMs.

  • Updates README.md to describe the chdb-arrow module plan as a v1.1.0-rc.1 validation release, with artifacts not yet published
  • Rewrites the RC guide in publishing.md: the RC workflow builds and tests artifacts but does not publish them; maintainers upload via the Vercel Maven gateway runbook, with version-path and overwrite checks in scripts/publish-rc-repository.sh, and consumers use https://maven.chdb.io without a GitHub PAT
  • Risk: tag pushes matching v*-rc.* no longer trigger the Central workflow — check the tag filter in release.yml matches the intended RC naming scheme

Macroscope summarized a3b02b8.

@ShawnChen-Sirius
ShawnChen-Sirius merged commit a0faf48 into main Nov 16, 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