Skip to content

Keep arrow with the pyo3-arrow that can hold it #29

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.

Sign up for GitHub

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

Merged
martin-s-a merged 1 commit into from
Oct 1, 2026
Merged

Keep arrow with the pyo3-arrow that can hold it #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions renovate.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,16 @@
"matchCurrentValue": "/^>=/",
"enabled": false
},
{
"description": [
"arrow and pyo3-arrow are one upgrade and not two: pyo3-arrow re-exports no arrow of its own, so the RecordBatch our arrow builds and the one PyRecordBatch::new takes have to come from the same major, or lib.rs does not compile.",
"pyo3-arrow 0.19, the newest there is, pins arrow 59, which is why arrow stops there. The cap is lifted in the same pull request that raises pyo3-arrow, never on its own.",
"Only arrow is capped. A pyo3-arrow release built against a newer arrow should open a PR that fails CI, which is the signal to do both by hand, rather than freeze silently.",
"The constraint is a bare version: cargo ranges are matched against each release, and a range here would filter out every one of them."
],
"matchDepNames": ["arrow"],
"allowedVersions": "<60"
},
{
"description": "Security advisories bypass the 14-day delay",
"matchUpdateTypes": ["security"],
Expand Down
Loading