Skip to content

bump pyo3 to 0.29.0 - #1472

Merged
arvidn merged 1 commit into
mainfrom
bump-pyo3-0.29.0
Jun 30, 2026
Merged

bump pyo3 to 0.29.0#1472
arvidn merged 1 commit into
mainfrom
bump-pyo3-0.29.0

Conversation

@arvidn

@arvidn arvidn commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

this addresses two cargo audit issues:

Crate:     pyo3
error: 2 vulnerabilities found!
warning: 9 allowed warnings found
Version:   0.27.1
Title:     Out-of-bounds read in `nth` / `nth_back` for `PyList` and `PyTuple` iterators
Date:      2026-06-11
ID:        RUSTSEC-2026-0176
URL:       https://rustsec.org/advisories/RUSTSEC-2026-0176
Solution:  Upgrade to >=0.29.0

Crate:     pyo3
Version:   0.27.1
Title:     Missing `Sync` bound on `PyCFunction::new_closure` closures
Date:      2026-06-11
ID:        RUSTSEC-2026-0177
URL:       https://rustsec.org/advisories/RUSTSEC-2026-0177
Solution:  Upgrade to >=0.29.0

@arvidn
arvidn requested a review from Rigidity June 29, 2026 14:34
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedcargo/​pyo3@​0.27.1 ⏵ 0.29.083 +2100 +18100100100

View full report

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: cargo target-lexicon

License: Apache-2.0 WITH LLVM-exception - The applicable license policy does not permit this license (5) (target-lexicon-0.13.5/LICENSE)

From: ?cargo/pyo3@0.29.0cargo/target-lexicon@0.13.5

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/target-lexicon@0.13.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@coveralls-official

Copy link
Copy Markdown

Coverage Report for CI Build 28379798107

Coverage decreased (-0.09%) to 81.496%

Details

  • Coverage decreased (-0.09%) from the base build.
  • Patch coverage: 25 uncovered changes across 13 files (0 of 25 lines covered, 0.0%).
  • 1 coverage regression across 1 file.

Uncovered Changes

Top 10 Files by Coverage Impact Changed Covered %
crates/chia-datalayer/src/merkle/format.rs 8 0 0.0%
crates/chia-datalayer/src/merkle/blob.rs 3 0 0.0%
crates/chia-consensus/src/owned_conditions.rs 2 0 0.0%
crates/chia-datalayer/src/merkle/proof_of_inclusion.rs 2 0 0.0%
crates/chia-protocol/src/program.rs 2 0 0.0%
crates/chia-bls/src/bls_cache.rs 1 0 0.0%
crates/chia-bls/src/gtelement.rs 1 0 0.0%
crates/chia-bls/src/public_key.rs 1 0 0.0%
crates/chia-bls/src/secret_key.rs 1 0 0.0%
crates/chia-bls/src/signature.rs 1 0 0.0%
Total (13 files) 25 0 0.0%

Coverage Regressions

1 previously-covered line in 1 file lost coverage.

File Lines Losing Coverage Coverage
crates/chia-datalayer/src/merkle/format.rs 1 86.0%

Coverage Stats

Coverage Status
Relevant Lines: 18899
Covered Lines: 15402
Line Coverage: 81.5%
Coverage Strength: 11945337.53 hits per line

💛 - Coveralls

@arvidn
arvidn merged commit 0fdd878 into main Jun 30, 2026
84 checks passed
@arvidn
arvidn deleted the bump-pyo3-0.29.0 branch June 30, 2026 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants