Repository navigation
chore(pyo3-object_store): Bump to pyo3 0.30 and prepare 0.13 release - #797
Merged
Merged
Conversation
Also bumps pyo3-async-runtimes to 0.30, and adds the unreleased R2 jurisdiction support (#757) to the changelog. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The in-repo pyo3-object_store now needs pyo3 0.30, but obstore is still on pyo3 0.29 (pyo3-arrow and pyo3-file have no 0.30 release yet), so the path dependency no longer resolves. Pin obstore to pyo3-object_store at the current main rev until obstore moves to 0.30. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kylebarron
marked this pull request as ready for review
October 15, 2026 14:22
kylebarron
added a commit
that referenced
this pull request
Oct 15, 2026
* chore: Bump obstore to pyo3 0.30 Bump pyo3 and pyo3-async-runtimes to 0.30 in the workspace, and move pyo3-file and pyo3-arrow to revs that use pyo3 0.30. Neither has a crates.io release with pyo3 0.30 yet, so pyo3-arrow is a git dependency on arro3 main for now. Switch pyo3-bytes and pyo3-object_store back to path dependencies. The git pin of pyo3-object_store from #797 predated #745, so main was running #745's regression tests against a pyo3-object_store without the fix, and test_head_with_prefix and test_open_reader_with_prefix failed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(pyo3-object_store): List the #745 prefix fix in the 0.13.0 changelog pyo3-object_store 0.13.0 was published from c8efd78, which includes #745, but the changelog entry was written before #745 merged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore: Use pyo3-arrow 0.20 from crates.io pyo3-arrow 0.20 is published with pyo3 0.30, so drop the git dependency on arro3 main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Apply suggestion from @kylebarron --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Note
This PR was written by Claude (Claude Code), not by @kylebarron.
Bumps
pyo3-object_storeto pyo3 0.30 and pyo3-async-runtimes 0.30, and its version to 0.13.0, with README and CHANGELOG entries. The changelog also lists the R2 jurisdiction URL support from #757, which hasn't been released yet.No code changes were needed. Clippy passes with
-D warningsagainst pyo3 0.30.1 and pyo3-async-runtimes 0.30.0 from crates.io.Temporary git dependency in
obstoreThis uses the same approach as #796.
obstorestays on pyo3 0.29 (pyo3-arrow and pyo3-file don't have 0.30 releases), so it usespyo3-object_store0.12 through a git dependency pinned tomainrev 174a0c8 rather than the in-repo path. Whenobstoremoves to 0.30, it should switch back to the path dependency.🤖 Written by Claude Code