Skip to content

chore(deps): drop stale pyo3 advisory ignores resolved by 0.29 #2125

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

Closed
chaliy wants to merge 1 commit into from
Closed

chore(deps): drop stale pyo3 advisory ignores resolved by 0.29 #2125

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
12 changes: 3 additions & 9 deletions deny.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,15 +38,9 @@ ignore = [
# Unmaintained build-time proc-macro in the bench harness only (not shipped
# library code); no upgrade available (tabled 0.21 is latest)
"RUSTSEC-2026-0173",
# pyo3: OOB read in PyList/PyTuple nth/nth_back (RUSTSEC-2026-0176)
# Patched in pyo3 >=0.29, but pyo3-async-runtimes has no 0.29 release yet
# (still pins pyo3 0.28), so we can't upgrade. Host-side Python bindings
# only — not reachable from sandboxed scripts. Remove on pyo3 0.29 bump.
"RUSTSEC-2026-0176",
# pyo3: missing Sync bound on PyCFunction::new_closure (RUSTSEC-2026-0177)
# Same 0.29 blocker; `new_closure` is not called anywhere in this
# workspace, so the unsound API is unreachable. Remove on pyo3 0.29 bump.
"RUSTSEC-2026-0177",
# NOTE: RUSTSEC-2026-0176 and RUSTSEC-2026-0177 (pyo3 OOB read / missing
# Sync bound) were resolved by the pyo3 0.29 bump (#2122); both ignores
# have been removed now that the workspace resolves pyo3 >=0.29.
]

[bans]
Expand Down
Loading