v0.127.2

A renamed releasable's past releases keep the tags they shipped under

Context

rlsbl monorepo rename-releasable's own rule is that historical releases stay under the old prefix, but the ref authority made the current scheme's spelling every archived version's primary ref, and the rename never recorded the spelling its past releases shipped under. In a renamed workspace, rlsbl release reconcile therefore planned to push new-name tags and create a second GitHub Release for every version whose Release already stands under its old tag.

The archive's shipped_as field now decides a version's primary ref, rename-releasable writes it, and re-running rename-releasable repairs a workspace renamed before it did. This reverses the earlier rule under which reconcile minted the current spelling for such versions; a tag or GitHub Release it already minted stays explained and counts as the version's own.

Fixes

• A renamed releasable's past releases keep the tags they shipped under. rlsbl release reconcile no longer plans new-name tags and duplicate GitHub Releases for versions released before rlsbl monorepo rename-releasable: a version whose archive records shipped_as keeps that tag as its primary ref, and a tag or Release under the current name still counts where one exists. rename-releasable now records shipped_as on every past release, and re-running it repairs a releasable renamed before it did. release edit, deprecate, yank, and retry find such a version's GitHub Release under its shipped tag.