ci: fix publish paimon-datafusion and python issue#253
Merged
JingsongLi merged 1 commit intoapache:release-0.1from Apr 16, 2026
Merged
ci: fix publish paimon-datafusion and python issue#253JingsongLi merged 1 commit intoapache:release-0.1from
JingsongLi merged 1 commit intoapache:release-0.1from
Conversation
Contributor
|
+1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Fix CI issues that block the 0.1.0 release:
paimon-datafusioncannot be published to crates.io because it depends on the unpublishedpaimonBrief change log
Rust crate publishing (
release-rust.yml):cargo publish --dry-runonly forpaimon(dry-run fails forpaimon-datafusionbecause it depends on the unpublishedpaimon)paimon, actively poll crates.io until the new version is indexed (up to 5 minutes, every 30 seconds) before proceeding to publishpaimon-datafusionWorkspace dependency refactor:
paimon = { version = "0.1.0", path = "crates/paimon" }to[workspace.dependencies]in rootCargo.tomlcrates/integrations/datafusion/Cargo.toml: switch frompaimon = { path = "../../paimon" }topaimon = { workspace = true }versionandpathPython wheel builds (
release_python_binding.yml):apt-get install libssl-dev(more reliable than the previous fallback)openssl11-develvia yum and create pkg-config symlinks (system OpenSSL 1.0.2 is too old foropenssl-sys).debpackages withar(no package manager needed inside the manylinux container)/usr/aarch64-unknown-linux-gnu/)opensslconf.h,configuration.h)CFLAGS_aarch64_unknown_linux_gnu="-D__ARM_ARCH=8"to fixringcrate ARM assembly compilationTests
Verified by running the release workflows on my own fork:
paimon→ wait for crates.io →paimon-datafusion)x86_64(manylinux2014) andaarch64(manylinux_2_28)API and Format
No API or storage format changes.
Documentation
No documentation updates required (CI-only changes).