Repository navigation
Resolve Security Audit failure by upgrading PyO3 and removing incompatible pythonize path - #284
Merged
Merged
Conversation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
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
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.
The scheduled
Security Auditworkflow failed ondictsqlite_v2/dictsqlitedue to two RustSec advisories affectingpyo3 0.28.2(RUSTSEC-2026-0176,RUSTSEC-2026-0177). This PR updates the vulnerable dependency chain and aligns the conversion path with available crate compatibility.Dependency remediation
pyo3from0.28to0.29indictsqlite_v2/dictsqlite/Cargo.toml.Cargo.lockto move the full PyO3 stack (pyo3,pyo3-ffi,pyo3-macros,pyo3-build-config, etc.) to0.29.0.Compatibility adjustment
pythonizedependency from the v2 crate because a0.29-compatible release is not available.pythonize::depythonizefast-path and uses the existing manual JSON conversion path consistently.Code path change (illustrative)