chore: bump regorus 0.2.8 → 0.10 to clear residual RUSTSEC-2026-0097#115
Merged
Conversation
The audit fix in PR #110 bumped rand 0.9.x to 0.9.4 but left the residual rand 0.8.5 in place (pulled by regorus 0.2.8). That instance was carried under an --ignore RUSTSEC-2026-0097 in supply-chain.yml and deny.toml with a comment "tracked for upstream resolution; sigil does not use custom rand loggers." regorus 0.10 is now out and drops the rand 0.8.5 transitive from the dep graph entirely. With it gone, the ignore entry in deny.toml and the matching --ignore flag in supply-chain.yml are no longer needed — cargo audit returns 0 vulnerabilities (excluding the unmaintained rustls-pemfile, which stays in the ignore list pending upstream deprecation). The regorus dep is feature-gated behind `--features rego` and is optional for power users of the Rego policy language; default builds do not use it. cargo build (default), cargo build --features rego, and cargo test --no-run --features rego all clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
avrabe
force-pushed
the
chore/regorus-0.10-bump
branch
from
0519cae to
49a5f75
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
5 tasks
avrabe
added a commit
that referenced
this pull request
May 16, 2026
Patch release bundling four PRs: #112 — Kani matrix fix + per-job tolerate_failure pattern #114 — Cerisier formalization companion docs (mapping + scenarios) #115 — bump regorus 0.2.8 → 0.10, fully clears RUSTSEC-2026-0097 #116 — second Verus admit attempt (theorem_pae_injective_on_types) Notable: cargo audit ignore-list is down to one entry (rustls-pemfile, unmaintained-upstream). No actively-fixable RUSTSEC advisories remain. Audit-related fixes from this release are summarised in the "Audit follow-ups" sections of the CHANGELOG. Issue #117 (Sigstore Fulcio cert rotation invalidated our pinned fingerprints) was surfaced during this cycle and is tracked separately — not blocking because audit C-4 documents that pinning is currently warn-only. Trace: skip Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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 audit fix in #110 bumped `rand` 0.9.x to 0.9.4 but left the residual `rand 0.8.5` in place (pulled transitively by `regorus 0.2.8`). That instance was carried under an explicit `--ignore RUSTSEC-2026-0097` in `supply-chain.yml` and `deny.toml` with the justification that wsc does not use custom rand loggers.
regorus 0.10 is now out and drops the `rand 0.8.5` transitive from the dep graph entirely. With it gone, the ignore entries are no longer needed.
Before / after
```
before: cargo audit → 1 vulnerability + 2 warnings (rand 0.8.5 ignored + rustls-pemfile unmaintained)
after: cargo audit → 0 vulnerabilities + 1 warning (rustls-pemfile unmaintained, still in ignore list pending upstream deprecation)
```
Changes
Test plan
Risk
regorus 0.2 → 0.10 is a major version jump and may have breaking changes in the public API. Since the dep is feature-gated and `wsc` only consumes a narrow surface, the build success above is the primary validation. If consumers of `--features rego` see API regressions, a targeted fix lands quickly.
Refs: audit M-1-adjacent supply-chain follow-up.