Repository navigation
Keep arrow with the pyo3-arrow that can hold it - #29
Merged
Merged
Conversation
Renovate has been offering arrow 60 since the 29th, and the pull request
cannot be made green. pyo3-arrow exports no arrow of its own, so the
RecordBatch star::read_all builds and the one PyRecordBatch::new accepts
are the same type only while both come from the same major. With arrow 60
in the graph and pyo3-arrow 0.19 holding arrow 59, lib.rs stops compiling:
error[E0631]: type mismatch in function arguments
note: expected function signature `fn(arrow::array::RecordBatch) -> _`
0.19 is the newest pyo3-arrow there is, from June, so there is nothing to
raise alongside it. arrow therefore stops below 60 until there is, and the
cap is lifted by whoever raises pyo3-arrow, in that same pull request.
Only arrow is capped. A pyo3-arrow built against a newer arrow should open
a pull request that fails CI, which is the signal to do both by hand,
rather than disappear into the dashboard.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
martin-s-a
added a commit
that referenced
this pull request
Oct 1, 2026
The constraint lives in renovate.json, where only Renovate reads it, and a human raising pyo3-arrow by hand would meet it as a compiler error. See #29. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
martin-s-a
added
bug
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
1 participant
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.
Closes the loop on #28, which cannot be made green.
pyo3-arrowexports noarrowof its own, so theRecordBatchthatstar::read_allbuilds and the onePyRecordBatch::newaccepts are the same type only while both come from the same major. With arrow 60 in the graph andpyo3-arrow0.19 holding arrow 59,src/lib.rsstops compiling, on every platform and every interpreter of the matrix:0.19 is the newest
pyo3-arrowpublished, from June, so there is nothing to raise alongside arrow. This caps arrow below 60 until there is, with the reason written next to the cap so that whoever lifts it knows it goes in the same pull request that raisespyo3-arrow.Only arrow is capped, deliberately. A
pyo3-arrowrelease built against a newer arrow should open a pull request that fails CI — the signal to do both by hand — rather than freeze silently, which is the same line this config already takes with the split Python pins.#28 can be closed once this lands; Renovate stops proposing 60 from then on.
🤖 Generated with Claude Code