Skip to content

fix(release): use distinct PyPI versions for each RC#330

Closed
luoyuxia wants to merge 1 commit into
apache:mainfrom
luoyuxia:fix-rc-version-publish-upstream
Closed

fix(release): use distinct PyPI versions for each RC#330
luoyuxia wants to merge 1 commit into
apache:mainfrom
luoyuxia:fix-rc-version-publish-upstream

Conversation

@luoyuxia
Copy link
Copy Markdown
Contributor

Summary

  • For pre-release tags (e.g. v0.2.0-rc1), override the version in pyproject.toml so each RC gets a unique PEP 440 version (e.g. 0.2.0rc1, 0.2.0rc2), avoiding Test PyPI overwrite conflicts
  • Maturin gives pyproject.toml precedence over Cargo.toml, so Cargo.toml remains untouched and Rust compilation is unaffected
  • Fix verification docs: correct package name (pypaimon-rust) and include RC number in pip install version

Test plan

🤖 Generated with Claude Code

When publishing RC tags (e.g. v0.2.0-rc1, v0.2.0-rc2) to Test PyPI,
the package version was always the base version (0.2.0) from Cargo.toml,
causing conflicts since Test PyPI does not allow overwriting.

For pre-release tags, override the version in pyproject.toml by replacing
`dynamic = ["version"]` with an explicit PEP 440 version (e.g. 0.2.0rc1).
Maturin gives pyproject.toml precedence over Cargo.toml, so Cargo.toml
remains untouched and Rust compilation is unaffected.

Also fix the verification docs: correct package name (pypaimon-rust)
and include the RC number in the pip install version.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@luoyuxia luoyuxia marked this pull request as draft May 19, 2026 12:34
@luoyuxia luoyuxia closed this May 19, 2026
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