panates / rman / 40281626208

95%

main: 95%

push

github

feat(version): `.rmanrc "carries"` - the packages a package's artifact carries without depending on them

A package carried into another's artifact by something no manifest records - a
Docker build context, a build that bundles a sibling's directory - now has a way
to say so. Each entry is a package name or a repository-relative directory, as in
`dependencies`. The listed packages count as the carrier's own: their commits
release it, its changelog lists them, and every publish target's dirty check
refuses to ship it while they have uncommitted changes.

A listed package is carried even when it takes its own version - a build context
is no dependency edge, so no cascade would reach the carrier otherwise. An entry
naming no package is an error.

Reported on syncbridge-io/syncbridge: syncbridge-engine's image takes web-ui/dist
through publish.docker.buildContexts, and two web-ui commits left it "no-change".
With `carries: ['@panates-prv/syncbridge-ui']` the plan reads 1.7.0 -> 1.8.0,
"changed since syncbridge-engine@1.7.0 (via @panates-prv/syncbridge-ui)".

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

4867 of 5319 branches covered (91.5%)

Branch coverage included in aggregate %.

67 of 67 new or added lines in 3 files covered. (100.0%)

25610 of 26767 relevant lines covered (95.68%)

280.78 hits per line