-
Notifications
You must be signed in to change notification settings - Fork 266
fix 0.5.x release cargo publish
#1379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix 0.5.x release cargo publish
#1379
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kevinjqliu for this fix!
im going to test the github action on my fork first before merging |
The ut failure is caused by generating doc. I think we could remove those docs for now. |
@@ -21,7 +21,9 @@ | |||
//! | |||
//! ## Scan A Table | |||
//! | |||
//! ```rust, no_run | |||
//! ```rust, ignore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@liurenjie1024 wdyt of using ignore
here for now? i didnt want to remove all the docs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's fine to me.
Which issue does this PR close?
What changes are included in this PR?
This PR removes
iceberg-catalog-memory
as a dev-dependency ofcrates/iceberg
. The dependency is not used and causedcargo publish
to fail during the 0.5.0 release (See #1325 (comment))This PR also changes
.github/workflows/release_python.yml
to depend onpublish.yml
since we only want to publishpyiceberg-core
to pypi after the crates are successfully published.https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#running-a-workflow-based-on-the-conclusion-of-another-workflow
Are these changes tested?
Yes, I tested the github action changes by pushing this PR to my fork's
main
and then push a new tag, with some minor changes so that the github action can run succesfully.The tag push triggered the
Publish
workflow (https://github.com/kevinjqliu/iceberg-rust/actions/runs/15265739052) which ran successfully and triggered thePublish Python 🐍 distribution 📦 to PyPI
workflow (https://github.com/kevinjqliu/iceberg-rust/actions/runs/15265757444)