Repository navigation
Conversation
Regenerating the harness lock for the Pantograph repin (#110) started from Pantograph's own lock, which rolled back crates #108 had already patched and reopened 21 Dependabot alerts: openssl 0.10.82 -> 0.10.75, rustls 0.23.46 -> 0.23.36, rustls-webpki 0.103.16 -> 0.103.9, tar 0.4.46 -> 0.4.44, bytes 1.12.1 -> 1.11.0 and rand 0.8.8 -> 0.8.5. Restore those with precise offline updates, and also move tokio, h2, crossbeam-epoch, anyhow and zstd/zstd-safe to the versions the main workspace already locks, which clears the remaining RUSTSEC findings. OSV now reports only the instant and pin-utils unmaintained notices that docs/SECURITY.md already accepts. The default offline, locked harness run passes 12 tests against the pinned Pantograph commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
|
Superseded: the Pantograph guard interop harness (and this lockfile) is being removed from Pumas entirely. Pantograph consumes Pumas through its public API; consumer-side compatibility checks belong in Pantograph. |
#110's regenerated harness lock (
rust/crates/pumas-core/tests/pantograph_guard_interop/Cargo.lock) started from Pantograph's own lock. It rolled back crates that #108 had already patched, which reopened 21 Dependabot alerts right after it merged.It also moves the crates behind the remaining RUSTSEC findings (which Scorecard reports) to the versions
rust/Cargo.lockalready uses:Every change is a
cargo update --offline -p <crate> --precise <version>. No manifest or Pantograph pin changes.Verification
--offline --locked) against the pinned Pantographd17b87epasses 12/12.instant(RUSTSEC-2024-0384) andpin-utils(RUSTSEC-2026-0441). Both are unmaintained notices thatdocs/SECURITY.mdalready accepts.🤖 Generated with Claude Code