panates / rman / 37314900224

95%

push

github

fix(publish): decide from the manifest publish writes, and keep --json stdout one document

2.11.1 read `private` from the build directory's package.json and treated
a missing one as "not built". That file is not what is published -
applyPlan writes its own derived manifest over it - and a build need not
write one: opra's @opra/common and @opra/client replace the preset's
build `after` step with their own esbuild step, had 625 and 52 built
files and no package.json, and the plan answered `error` for both,
stopping opra's release after its version had been pushed.

- `private` comes from the derived manifest: the source's, kept only
  without a publishConfig; in place, the source's own.
- A build directory that is missing or holds only a package.json is the
  error now, not one without a package.json.
- publish's failure line goes to stderr: under --json it was printed to
  stdout below the plan, which no JSON reader accepts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

3462 of 3766 branches covered (91.93%)

Branch coverage included in aggregate %.

45 of 45 new or added lines in 2 files covered. (100.0%)

20500 of 21517 relevant lines covered (95.27%)

219.04 hits per line