fix(ci): restore main's yarn.lock clobbered by the upstream sync merge

Browse Source

- Problem: CI's yarn legs fail on ea0a6ff6 with YN0028 (lockfile would be
  modified) - the sync merge commit carries a locally regenerated
  yarn.lock (2a02200e) even though both merge parents ship the identical
  lockfile (7b566ee0), so the merged tree's package.json no longer
  matches the committed lockfile.
- Fix: restore yarn.lock to the parents'/main's blob (7b566ee0), which
  is the exact combination CI validates green on main and validated
  green on ddef0301 (46/46).
- Verification: yarn install --mode=skip-build (CI's exact step,
  COREPACK_ENABLE_STRICT=0, skip-build) exits 0 and leaves yarn.lock
  unmodified; tree content otherwise identical to ea0a6ff6, whose full
  suite passed 704/0 locally.

...

This commit is contained in:

Santhi Prakash

2026-10-02 04:10:28 +00:00

parent ea0a6ff61a

commit 214eecc81f

1 changed files with 2190 additions and 1471 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

yarn.lock

+2190 -1471

File diff suppressed because it is too large Load Diff