andygrove opened a new pull request, #1695: URL: https://github.com/apache/datafusion-python/pull/1695
# Which issue does this PR close? N/A — this is release follow-up maintenance, matching the equivalent change made for DataFusion 54 in #1588. # Rationale for this change `main` currently pins the DataFusion crates to the `55.0.0-rc3` git tag via `[patch.crates-io]`. DataFusion 55.0.0 has since been published to crates.io, so the patch is no longer needed. The patch entries also block publishing: `dev/check_crates_patch.py` (run by the `check-crates-patch` CI job) fails while any entries are present, since release builds must not depend on patched crates. # What changes are included in this PR? - Remove all `[patch.crates-io]` entries from `Cargo.toml`. The section header and its explanatory comment are kept (an empty section is explicitly allowed by `dev/check_crates_patch.py`), so future development patches have an obvious home. - Regenerate `Cargo.lock` so the DataFusion crates resolve from the crates.io registry instead of `git+https://github.com/apache/datafusion?rev=55.0.0-rc3`. The declared dependency versions in `[workspace.dependencies]` were already `55.0.0`, so no version numbers changed and no source changes were required. # Are there any user-facing changes? No. The resolved DataFusion version is unchanged — 55.0.0-rc3 and the 55.0.0 release are the same code, only the source moves from git to crates.io. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
