chore(ci): ignore pyo3 RUSTSEC-2026-0176 and -0177 in audit#2637
Merged
blackmwk merged 2 commits intoJun 15, 2026
Merged
Conversation
These two advisories affect pyo3 < 0.29. pyo3 is pulled only transitively through arrow's `pyarrow` feature (arrow-pyarrow), whose latest release still pins pyo3 ^0.28, so no dependency upgrade can clear them yet. Ignore them, matching how the existing transitive advisories are handled, until arrow-pyarrow moves to pyo3 >=0.29.
blackmwk
approved these changes
Jun 15, 2026
blackmwk
left a comment
blackmwk
left a comment
Contributor
There was a problem hiding this comment.
Thanks @NoahKusaba for this fix!
This was referenced Jun 15, 2026
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
2 participants
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.
These two advisories affect pyo3 < 0.29. pyo3 is pulled only transitively through arrow's
pyarrowfeature (arrow-pyarrow), whose latest release still pins pyo3 ^0.28, so no dependency upgrade can clear them yet. Ignore them, matching how the existing transitive advisories are handled, until arrow-pyarrow moves to pyo3 >=0.29.Which issue does this PR close?
Fix existing security audit fail
What changes are included in this PR?
Are these changes tested?