fix(deps): regenerate Cargo.lock to dedupe wasmparser (unblocks #98 + every cargo CI run)#99
Closed
hyperpolymath wants to merge 1 commit into
Closed
fix(deps): regenerate Cargo.lock to dedupe wasmparser (unblocks #98 + every cargo CI run)#99hyperpolymath wants to merge 1 commit into
hyperpolymath wants to merge 1 commit into
Conversation
Cargo.lock had three wasmparser entries — a stale 0.250.0 (no longer referenced; Cargo.toml requires `=0.251.0`) plus two competing 0.251.0 copies differing in dependency set (one with `hashbrown` + `serde`, one without). This caused `cargo build --workspace --locked` to fail with "package `wasmparser` is specified twice in the lockfile" on every commit since Dependabot PR #91 landed. Regenerated via `rm Cargo.lock && cargo generate-lockfile`. Single `wasmparser 0.251.0` entry now resolved. Why this matters: blocks PR #98 ([draft] -> [review] promotion for proposals 0001 + 0002) and every other PR's `Cargo build + test` check. Phase 0 #48 explicitly requires green CI on main. Validation: - `cargo build --workspace --locked` -> ok - `cargo test --workspace --locked` -> all green (incl. cross-compat + property + 5 fixture tests) Refs #48
🔍 Hypatia Security ScanFindings: 96 issues detected
View findings[
{
"reason": "Action perpolymath/standards/.github/workflows/governance-reusable.yml@main\n needs attention",
"type": "unpinned_action",
"file": "governance.yml",
"action": "pin_sha",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in boj-build.yml",
"type": "unknown",
"file": "boj-build.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in c5-regenerate.yml",
"type": "unknown",
"file": "c5-regenerate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in cargo-audit.yml",
"type": "unknown",
"file": "cargo-audit.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "unknown",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
hyperpolymath
added a commit
that referenced
this pull request
May 30, 2026
…isible text The asciidoc link macro's visible text matched the local-path-resolution heuristic of `Aspect (claim envelope)` test #8 (`Path references in docs resolve to real files`), which interpreted the bracketed display string `nextgen-languages/docs/disambiguation/ephapax-vs-affinescript.md` as a path inside *this* repo and reported it stale (file does live under hyperpolymath/nextgen-languages — the URL target is correct; only the visible text triggered the false positive). Change visible text to a prose label that doesn't look like a relative path. URL target unchanged. Unblocks PR #99 and every other typed-wasm cargo CI run currently failing on Smoke test for the same envelope-check violation. Refs #99
Owner
Author
|
Closing — same Cargo.lock dedup already shipped via #105 (merged 2026-05-30 13:31Z). Parallel-session duplicate; this branch's content is now redundant. |
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
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.
Summary
Cargo.lockregenerated to remove a duplicatewasmparser 0.251.0entry + a stalewasmparser 0.250.0entry left behind by Dependabot PR chore(deps): bump wasmparser from 0.250.0 to 0.251.0 #91cargo build --workspace --lockedandcargo test --workspace --lockedgo green locallyCargo.tomledits, no code, no docsWhy
Since PR #91 (
bump wasmparser from 0.250.0 to 0.251.0, merged 2026-05-30 08:23Z) every CI run onmainand every open PR has been failing Cargo build + test (typed-wasm-verify) with:Local reproduction:
The lockfile had three wasmparser entries:
crates/typed-wasm-verify/Cargo.tomlrequireswasmparser = "=0.251.0", so the 0.250.0 entry is unreferenced (left behind during the bump) and the second 0.251.0 entry is a degenerate duplicate.Fix:
rm Cargo.lock && cargo generate-lockfileproduces a singlewasmparser 0.251.0entry (withhashbrown+serde, matching whatcargo fetchactually resolves today).Impact
Directly unblocks:
Cargo build + testcheckmain-side bug, not PR-introduced)Contributes to Phase 0 #48's "every commit on main exits CI green" gate (currently broken for cargo).
What this PR does NOT do
=0.251.0exact-pin policy is preserved per the comment incrates/typed-wasm-verify/Cargo.tomllines 22-26)Smoke testred (claim-envelope finds 1 stale doc-pathnextgen-languages/docs/disambiguation/ephapax-vs-affinescript.mdin README.adoc:36 — separate fix worth filing)Test plan
cargo build --workspace --locked-> okcargo test --workspace --locked-> all green (39+ tests across unit + cross-compat + property + 5 fixture tests)grep -c '^name = "wasmparser"' Cargo.lock-> 1)Refs