fix(ci): log yarn.lock state after tarsync (debug)#1798
Conversation
…ows failures After tarsync runs yarn install in the test project, check whether yarn.lock was created and whether it contains the root-workspace- entry. This surfaces the failure that tarsync currently swallows silently before yarn cedar g secret fails with the lockfile error. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
👷 Deploy request for cedarjs pending review.Visit the deploys page to approve it
|
Greptile SummaryAdds diagnostic logging after
Confidence Score: 5/5This is a purely additive diagnostic-only change that inserts logging after tarsync and before the already-guarded secret generation step; it cannot affect CI outcomes in any direction. Both previously reported bugs (off-by-one line count and wrong startsWith prefix for Yarn Berry v4 quoted keys) are corrected in this version. The new code reads a file synchronously for logging only and has no effect on the surrounding async flow. No files require special attention. Important Files Changed
Reviews (4): Last reviewed commit: "chore: prettier" | Re-trigger Greptile |
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx run-many -t build:pack --exclude create-ceda... |
✅ Succeeded | 2s | View ↗ |
nx run-many -t test --minWorkers=1 --maxWorkers=4 |
✅ Succeeded | 8s | View ↗ |
nx run-many -t test:types |
✅ Succeeded | 10s | View ↗ |
nx run-many -t build |
✅ Succeeded | 6s | View ↗ |
☁️ Nx Cloud last updated this comment at 2026-05-16 16:47:31 UTC
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx run-many -t test --minWorkers=1 --maxWorkers=4 |
✅ Succeeded | 8s | View ↗ |
nx run-many -t build:pack --exclude create-ceda... |
✅ Succeeded | 7s | View ↗ |
nx run-many -t test:types |
✅ Succeeded | 10s | View ↗ |
nx run-many -t build |
✅ Succeeded | 6s | View ↗ |
☁️ Nx Cloud last updated this comment at 2026-05-16 10:56:46 UTC
|
The changes in this PR are now available on npm. Try them out by running Or try it in a new app with |

Summary
Adds diagnostic logging after
yarn project:tarsync --verboseruns in the test project setup, to help understand the intermittent Windows CI failure whereyarn cedar g secret --rawfails with:What this adds
After tarsync completes, we now check:
yarn.lockget created at all? (tarsync's internalyarn installerrors are silently swallowed — we'd never know if it didn't run)The next time this fails on Windows, the log will show one of:
WARNING: yarn.lock was not created by tarsync!→ tarsync's yarn install didn't run or failed very earlyWARNING: yarn.lock exists but has no root-workspace- entry!→ yarn install ran but produced an incomplete lockfileRoot workspace entry found: root-workspace-...→ lockfile is fine, look elsewhere for the failureRelates to the investigation in
docs/implementation-plans/flaky-windows-smoke-tests-investigation.md.Test plan
🤖 Generated with Claude Code