The 0.90.0-rc branch was promoted (merged) into `stable` carrying the
release-candidate versions `c2pa 0.90.0-rc.3` / `c2patool 0.27.0-rc.3`.
release-plz's `release-pr` step then aborted with:

    local package `c2pa` has a greater version (0.90.0-rc.3) with respect
    to the registry package (0.89.3), but the git tag c2pa-v0.90.0-rc.3
    exists.

release-plz's guard matches a git tag against the exact local version, and
`release-rc.yml` had already created `c2pa-v0.90.0-rc.3` (a prerelease
binary-build tag, never published to crates.io). release-plz reads that
tag as an unpublished-but-tagged release and refuses to proceed.

Stripping the prerelease suffix to the final `0.90.0` / `0.27.0`:

  * removes the collision without deleting any RC tags -- the guard now
    looks for `c2pa-v0.90.0`, which does not exist; the `-rc.N` tags no
    longer match the local version, and
  * pins the release to the exact versions whose binaries were baked and
    validated as `-rc.3`, rather than letting release-plz recompute each
    crate's bump independently (which could land c2patool on 0.26.73
    instead of the train's intended 0.27.0).

release-plz still authors the changelog release-PR and performs the
publish; the manual version simply acts as the floor.

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