panates / rman / 36586197834

95%

push

github

feat(version): a "version.stamp" entry may be optional

A listed file that exists and holds nothing rewritable is an error, and that is
right: a missing file means "not this package", while an existing one with nothing
to rewrite means somebody asked for something and did not get it - and silence there
ships a stale constant on every release from then on.

But "somebody" is not always the repository. A shared preset naming
`src/constants.ts` for every package of a technology is saying "stamp it where there
is one", and cannot know which of forty consumers actually keeps a version constant
there. Measured on panates/postgrejs, which extends @panates/rman-preset: the file
exists, has never held a version constant (`git log -S"export const version" --
src/` is empty), and `rman version` refused the release over a line nobody in that
repository wrote.

So the asker says which it meant. `{ file, optional: true }` waives the refusal; a
bare string still throws, which is what catches a typo'd path or a renamed
identifier. It is the file.exists() / file.resolve() split again - the optional form
and the throwing form, chosen by the caller.

The two specs are each other's control: same file, same missing constant, opposite
outcome. A third pins that `optional` waives the refusal and not the work - a file
that does hold a version is still stamped, or "skip it" and "ignore the entry" would
be indistinguishable.

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

2916 of 3197 branches covered (91.21%)

Branch coverage included in aggregate %.

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

17613 of 18590 relevant lines covered (94.74%)

197.6 hits per line