From 6d4f24e7fe5e86916627590d2ccba5f0a4dd2aeb Mon Sep 17 00:00:00 2001 From: Otavio Salvador Date: Sun, 14 Jun 2026 23:17:09 -0300 Subject: [PATCH] docs: note that v1.0.1 was amended post-publish Record the deliberate exception to the immutable-tag rule: v1.0.1 (and v1) were force-moved on 2026-06-15 to fix a placeholder-commit-message regression, rather than cutting v1.0.2, because the release had negligible adoption. --- docs/releasing.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/releasing.md b/docs/releasing.md index ec09262..21dd973 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -29,3 +29,13 @@ Two kinds of tags, both on the same release commit: For a docs/non-release change that should reach `@v1` callers without a new version, just move the major tag: `git tag -f v1 HEAD && git push -f origin v1`. + +## Exceptions + +- **`v1.0.1` was amended after publishing (2026-06-15).** It shipped with a + regression that made `update-flake` PRs land a placeholder commit message + (`[create-pull-request] automated change`). Because adoption was negligible, + the fix was force-pushed onto the existing `v1.0.1` and `v1` tags instead of + cutting a `v1.0.2`. This is a deliberate one-off departure from the immutable + `vX.Y.Z` rule above; don't treat it as precedent for moving published patch + tags once a release has real users.