Skip to content

fix(deps): restore patched crates in the interop harness lock - #112

Closed
MrScripty wants to merge 1 commit into
mainfrom
deps/interop-harness-lock-repatch
Closed

MrScripty wants to merge 1 commit into
mainfrom
deps/interop-harness-lock-repatch

Conversation

@MrScripty

Copy link
Copy Markdown
Owner

#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.

Crate Before #110 After #110 This PR
openssl (+ openssl-sys) 0.10.82 0.10.75 0.10.82
rustls 0.23.46 0.23.36 0.23.46
rustls-webpki 0.103.16 0.103.9 0.103.16
tar 0.4.46 0.4.44 0.4.46
bytes 1.12.1 1.11.0 1.12.1
rand (0.8 line) 0.8.8 0.8.5 0.8.8

It also moves the crates behind the remaining RUSTSEC findings (which Scorecard reports) to the versions rust/Cargo.lock already uses:

  • tokio 1.49.0 → 1.54.1
  • h2 0.4.13 → 0.4.16
  • crossbeam-epoch 0.9.18 → 0.9.20
  • anyhow 1.0.100 → 1.0.104
  • zstd 0.13.3 → 0.13.4 and zstd-safe 7.2.4 → 7.4.0

Every change is a cargo update --offline -p <crate> --precise <version>. No manifest or Pantograph pin changes.

Verification

  • The default harness run (--offline --locked) against the pinned Pantograph d17b87e passes 12/12.
  • An OSV query over all 368 registry packages in the lock reports only instant (RUSTSEC-2024-0384) and pin-utils (RUSTSEC-2026-0441). Both are unmaintained notices that docs/SECURITY.md already accepts.

🤖 Generated with Claude Code

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>
@coderabbitai

coderabbitai Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c30164d5-a13a-4ec2-b1e6-0cb14ea44b91
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

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.

Share

@MrScripty

Copy link
Copy Markdown
Owner Author

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.

@MrScripty MrScripty closed this Nov 6, 2026
@MrScripty
MrScripty deleted the deps/interop-harness-lock-repatch branch November 6, 2026 18:50
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.

1 participant