| commit | 48433cbc219a046c471f41e3f2aed589346d82e4 | [log] [tgz] |
|---|---|---|
| author | Kevin Liu <kevinjqliu@users.noreply.github.com> | Mon May 26 23:52:04 2025 -0400 |
| committer | GitHub <noreply@github.com> | Mon May 26 23:52:04 2025 -0400 |
| tree | 62c67e9631dce9db7a461067c370c1471df211c8 | |
| parent | 18a44cd7f31d07cea3284b702f269c1affe4ffbc [diff] |
fix 0.5.x release `cargo publish` (#1379) ## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123. --> - Closes #. ## What changes are included in this PR? <!-- Provide a summary of the modifications in this PR. List the main changes such as new features, bug fixes, refactoring, or any other updates. --> This PR removes `iceberg-catalog-memory` as a dev-dependency of `crates/iceberg`. The dependency is not used and caused `cargo publish` to fail during the 0.5.0 release (See https://github.com/apache/iceberg-rust/issues/1325#issuecomment-2910782152) This PR also changes `.github/workflows/release_python.yml` to depend on `publish.yml` since we only want to publish `pyiceberg-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? <!-- Specify what test covers (unit test, integration test, etc.). If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> 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 the `Publish Python š distribution š¦ to PyPI` workflow (https://github.com/kevinjqliu/iceberg-rust/actions/runs/15265757444)
Rust implementation of Apache Icebergā¢.
The Apache Iceberg Rust project is composed of the following components:
| Name | Release | Docs |
|---|---|---|
| iceberg |  |   |
| iceberg-datafusion |  | |
| iceberg-catalog-glue |  | |
| iceberg-catalog-hms |  | |
| iceberg-catalog-memory |  | |
| iceberg-catalog-rest |  | |
The features that Iceberg Rust currently supports can be found here.
Iceberg Rust is built and tested with stable rust, and will keep a rolling MSRV(minimum supported rust version). At least three months from latest rust release is supported. MSRV is updated when we release iceberg-rust.
Check the current MSRV on crates.io.
Apache Iceberg is an active open-source project, governed under the Apache Software Foundation (ASF). Iceberg-rust are always open to people who want to use or contribute to it. Here are some ways to get involved.
The Apache Iceberg community is built on the principles described in the Apache Way and all who engage with the community are expected to be respectful, open, come with the best interests of the community in mind, and abide by the Apache Foundation Code of Conduct.
Licensed under the Apache License, Version 2.0