You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c17f305
Browse filesBrowse the repository at this point in the historyBrowse files
A pnpm-workspace.yaml that is empty or holds only comments or document
markers reads as "no workspace" to pnpm. Hosted scans appended only
`trustLockfile: true` and vendored scans only an `overrides:` block to
such a file, and pnpm 8.x-10.4 then refused every command with
"packages field missing or empty", even though the scan reported
success.
Both writers now splice the root-only `packages: ['.']` scaffold in
with their key when the file has no keys, and follow the no-file #734
rule: a project pinned to pnpm 9.0-10.4 gets no workspace edit. Hosted
rollback and vendored revert take the spliced lines back out, so the
user's file comes back byte for byte (an empty file reads as the
created scaffold and is deleted by hosted rollback, as before).
Fixes#1096
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
0 commit comments