Skip to content

docs: note that v1.0.1 was amended post-publish #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
otavio wants to merge 1 commit into from
Closed

docs: note that v1.0.1 was amended post-publish #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/releasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.