panates / rman / 36999673499

95%

push

github

feat(changelog): changelog.groupFiles - put a named group's file where it belongs

Under `groupBy: 'group'` the default group's file was already movable through
`changelog.filePath`, but a named group always went to the repository root as
`CHANGELOG-<group>.md`. Now a root-level map sets it per group, relative to the
repository root:

    changelog:
      groupBy: group
      groupFiles:
        core: packages/core/CHANGELOG.md

An unlisted group keeps the old rule, so no repository changes until it names
one. Read off the root only, for the reason `groupBy` is: which file a group
shares is a layout, and per package two members could disagree about it.

**Refused before anything is written, because each is silent otherwise:**

- a key naming no group - rman drops an unknown config key without a word, so a
  typo would leave the group on the default rule; the groups are known here, so
  the error can list them;
- a path outside the repository - `version --changelog` commits the file with
  the release;
- two groups resolving to one file, the default group and solo packages
  included. Each file carries one `documented-up-to` marker, so two groups
  sharing it would each read the other's boundary - entries missing or doubled,
  nothing failing. This also catches an *unlisted* group whose suffixed default
  lands on a listed path, and is checked over the whole repository rather than
  the run's targets: verified by narrowing the check to targets, under which a
  `--scope` leaving one group out let the collision through.

An explicit `--file-path` overrides the map for that run, as it already beats
`changelog.filePath`, and still suffixes named groups so they cannot collide.

`version --changelog` needed no change: it keys the file to the group's commit
by the path the changelog call returned. Pinned end to end - a group mapped into
`packages/a/` has its file in the commit its tag names, with a clean tree.

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

3297 of 3596 branches covered (91.69%)

Branch coverage included in aggregate %.

146 of 153 new or added lines in 2 files covered. (95.42%)

19856 of 20892 relevant lines covered (95.04%)

212.03 hits per line