v0.128.0

New rlsbl rewrite project-name command renames a standalone project's published identity: npm and PyPI package names, the Go module path, and the identity-transition record.

Context

A standalone project could not rename its published identity through rlsbl:
monorepo rename-releasable covers releasables and rewrite go-module-path covers
a Go module path, but nothing renamed the package names in the manifests or
recorded the change. The new command renames the package name in every target
manifest whose target renames it, moves the Go module path to one ending in the
new name, and records one identity-transition event per changed identity. The
Go event starts from the module path the latest release published, read from
go.mod at that release's commit. Every event's effective version is the version
the next release ships, decided by the same rule the release flow applies. The
rename and the record are two commits, so a re-run completes an interrupted
rename. Every release target now declares whether rlsbl renames its package
name, and where that name is declared.

Features

• New command rlsbl rewrite project-name --from <old> --to <new>. Renames a standalone project's published identity: the package name in its npm and PyPI manifests and, for a Go target, the module path's last element. It records one identity-transition event per changed identity, effective from the version the next release ships (the Go event starts from the module path the latest release published), commits the rename and the record separately so a re-run completes an interrupted one, and lists the remaining steps: source directories, install_paths, rlsbl scaffold, command names, the GitHub repository, and a breaking changelog entry. Every release target now declares whether rlsbl renames its package name.