fix(security): remediate tract-nnef advisory - #436
Conversation
|
Warning Review limit reached
Next review available in: 22 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Change contract
Update the ONNX inference dependency from tract 0.21 to the patched 0.22 line, removing
RUSTSEC-2026-0217from the locked dependency graph.Acceptance evidence
cargo auditreportedRUSTSEC-2026-0217fortract-nnef 0.21.10.cargo auditreports zero instances of that advisory.cargo test -p hft-infer-onnx --lockedcargo test -p hft-strategy-dl --lockedOut of scope
Polymarket Gate admission, collectors/uploaders, production cutover, research, and snapshots.
Dependency or merge order
Independent of #433 / #434. Merge before #434 because the repository-required Cargo audit currently blocks #434 against the same unchanged lockfile.
Rollout / rollback impact
No runtime deployment in this PR. The dependency update is reverted by reverting this PR; #434 remains separately rollbackable.