Skip to content

Ignore the other pyo3 RUSTSEC advisory #8460

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
AdamGS merged 1 commit into from
Jun 17, 2026
Merged

Ignore the other pyo3 RUSTSEC advisory #8460

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
5 changes: 4 additions & 1 deletion deny.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,10 @@ ignore = [
# 0.29.0. We cannot bump until pyo3-bytes, pyo3-log, and pyo3-object_store support 0.29 (all
# pin pyo3 to <0.29, and pyo3-ffi `links = "python"` forbids two pyo3 versions in the graph).
# Not exploitable here: `vortex-python` never calls `nth`/`nth_back` on these iterators.
"RUSTSEC-2026-0176"
"RUSTSEC-2026-0176",
# Another issue that will be fixed once we can bump pyo3 to 0.29.
# PyCFunction::new_closure is missing a `Sync` bound.
"RUSTSEC-2026-0177"
]

[licenses]
Expand Down
Loading