Commit Graph
9 Commits
Author SHA1 Message Date
Daz DeBoerandClaude Opus 5 b7d46eb472 Document immutable releases in the release process
Release immutability is now enabled for this repository, so a published
release permanently locks its Git tag to a commit, and deleting the
release does not free the tag name for reuse.

Reorder the steps so the signed tag is created and pushed before the
release is drafted, and have the draft select that existing tag. Letting
GitHub create the tag at publish time produces an unsigned, lightweight
tag pointing at whatever main resolves to at that moment - both of which
immutability then makes permanent.

Also record that the v6 major tag must never have a release attached:
immutability locks only tags that have a release of their own, which is
what keeps the conventional major-tag force-push legal.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-02 13:54:30 -06:00
Daz DeBoerandGitHub 20ce680c89 Update RELEASING.md 2026-06-09 19:55:28 -06:00
Daz DeBoer c2457a7fb2 Update tagging instructions for release 2026-03-23 17:46:33 -06:00
Jerome Prinet 6f229686ee Upgrade gradle/actions to v5 2025-10-01 12:23:40 +02:00
Daz DeBoerandGitHub 57d85d9e4d Update release process to include tag signing 2025-04-02 12:11:44 -06:00
Daz DeBoerandGitHub d724da5563 Update RELEASING.md for v4 2024-08-07 11:41:14 -06:00
Daz DeBoerandGitHub 9edf610422 Update RELEASING.md for v4 2024-08-04 15:14:38 -06:00
daz 0fa10b26b8 Update releasing guide 2024-04-12 14:01:48 -06:00
Daz DeBoerandGitHub 6232a3f503 Documentation improvements (#132)
- Add `RELEASING.md` to document the release process
- Mention the recommendation to disable local build-cache when remote
build-cache is available. Fixes #102
2024-04-08 19:19:50 -06:00