panates / rman / 39380848216

95%

main: 95%

push

github

feat(version): an unpublished package's commits count for the published packages carrying it

A package kept out of publishing takes no version (2.22), and its commits
counted for nobody - so a published package that ships it inside its own
artifact never released for a change to it. Measured on
panates/syncbridge-cloud: the Docker-only server bundles four publish.skip
workspace packages, a fix to services (a348f94f) left the server
`no-change`, and the image would never have carried the fix.

A published package's commits now include those of its run-time in-repo
dependencies that take no version, transitively, stopping at a versioned
one (`bundledPackages`). The reason names them: "changed since <tag>
(via services)". The same rule drives the planner's dirty check, the
changelog's commit attribution, and the dirty check of the npm, docker
and cloudflare targets, so a release is never cut for a fix its notes
leave out, nor an artifact built from a carried package's uncommitted
changes.

Only run-time edges count, through the new optional
`ManifestProvider.runtimeDependencies` - npm answers dependencies,
optionalDependencies and non-optional peers - so a test helper does not
release every library that tests with it. A provider with no answer counts
every dependency.

`unversionedReason` moves to utils, as `groupKeyOf` did, since the
changelog asks it with no planner registered; `notVersionedReason` stays
protected and delegates.

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

4575 of 5003 branches covered (91.45%)

Branch coverage included in aggregate %.

166 of 167 new or added lines in 8 files covered. (99.4%)

24422 of 25549 relevant lines covered (95.59%)

263.93 hits per line