fix(deps): bump pyo3 to 0.29.0 (RUSTSEC-2026-0176 / RUSTSEC-2026-0177)#388
Merged
Conversation
…6-0177) Two advisories published 2026-06-11 against pyo3 <0.29.0 (out-of-bounds read in PyList/PyTuple iterator nth/nth_back; missing Sync bound on PyCFunction::new_closure) turned the Security Audit gate red on every branch. llmtrace-python does not call the affected APIs directly, but the audit gate is binary. Migration: pyo3 0.29 removed the PyObject alias — replaced with Py<PyAny> throughout lib.rs. No other API changes were needed; clippy clean under -D warnings.
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.
What
Two RUSTSEC advisories published 2026-06-11 against pyo3 <0.29.0 turned the Security Audit gate red on every branch (first seen on #387, a docs-only PR; main's last green run predates the advisories):
nth/nth_backforPyList/PyTupleiteratorsSyncbound onPyCFunction::new_closureclosuresllmtrace-pythondoes not call the affected APIs directly (noPyList/PyTupleiteration, nonew_closure), but the audit gate is binary and correctly so.Migration
pyo3 0.24.2 → 0.29.0. The only breaking change that bit: the
PyObjectalias was removed — replaced withPy<PyAny>throughoutlib.rs(6 sites, mechanical). Lockfile updates pyo3* crates only (plus dropping the now-unusedunindent).Evidence
cargo build -p llmtrace-python: cleanRUSTFLAGS="-D warnings" cargo clippy -p llmtrace-python --all-targets: cleancargo fmt --all --check: clean