panates / rman / 37296752672

95%

push

github

fix(publish): decide private from the manifest that will be published

`getPlan` read `private` from the source package.json while
`derivePublishManifest` removed it from what it ships, so a single-package
repository whose source carried `private: true` as a guard against a stray
`npm publish` answered `skip - private package` and published nothing,
with version, tag and GitHub release all going through.

- The plan reads the build directory's package.json when the package
  publishes from one, its own otherwise.
- `private` leaves a derived manifest only when the package declares a
  `publishConfig`; `private` alone still means private.
- A build directory with no package.json is an error: nothing was built.
- A package private in its source with no publishConfig is skipped before
  the build is looked for, so unbuilt private packages do not error.
- `--contents` is a plan option now, since the plan reads that directory.

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

3450 of 3758 branches covered (91.8%)

Branch coverage included in aggregate %.

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

20469 of 21499 relevant lines covered (95.21%)

217.51 hits per line