Repository navigation
Conversation
pnpm 12 writes the env lockfile (pnpm itself) as a first YAML document before the main lockfile. The single-document load raised ComposerError, so every front-end PR that changed the lockfile got the false hard block "incomplete dependency data". Read every document with the same unique-key safe loader. Accept one document, or exactly two with an env document of the known shape. Each document needs a supported lockfileVersion, and every env dependency needs a packages entry. Packages from both documents get every check. Anything else stays a parse failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review of 01d3cb3 found that an env package entry could take another package's identity through its own name and version, so pnpm could pass the env check and then skip every check. The env check now refuses an entry whose name or version differs from its key, and checks each env dependency against the packages the walker emits. The main document of a two-document file had no shape check. It may now hold only the top-level keys of pnpm 12's main lockfile. The one-document form keeps its old check. The shared YAML loader expands merge keys before the duplicate-key check, so a merged key that repeats another key is a parse failure. Tests cover both scenarios, cross-document aliases, unsafe tags in each document, merge-key collisions, end markers, a BOM, a document marker in a block scalar, and a malformed two-document base in collect (K-10). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🔴 FAIL: OC Claude review did not completeCaution Incomplete file coverage blocks this PR. No waiver can clear it.
Run 40909207812, attempt 1 for head 📋 Full review record: reasons, checks, signals, finding details, model summaries, token usageReviewed snapshot
Reasons the gate failed
No waiver line is shown. At least one reason cannot be waived, so a waiver would not change the result. Checks (code, no model)
Signals (context only, never block)
Dependency changes None. Finding details
Blocking is decided by code from category and severity, never by the model. A finding in a blocking category blocks only at high or critical severity. No findings from the passes that ran. The Review, Security, Supply chain pass did not run, so this is not a clean result. Model summaries
Token usage
|
|
Combined into #20. |
Fixes the first pilot false positive.
pnpm 12 writes
pnpm-lock.yamlas two YAML documents: an env lockfile (the package manager itself) and the normal lockfileVersion 9.0 lockfile. The parser loaded one document, so every OperationCode/front-end PR that touched the lockfile hit the hard block "dependency data incomplete: does not parse" (first seen on front-end#2027).Real lockfiles parse: front-end PR head (1602 packages) and main (1604). Unit tests 2668 passed; release tests 2 passed. Eval not run.
Review: adversarial review (other model family) found 2 Important + 1 Minor; all fixed with tests; scoped re-review clean. Open minor (pre-existing): nested merge aliases grow about 2^depth before the duplicate check; only the byte cap limits it.
Goes live only with a release (Console job_workflow_ref + both rulesets' sha).
🤖 Generated with Claude Code