Skip to content

Document the release tag ruleset #4

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

Merged
PavlosIsaris merged 1 commit into from
Sep 30, 2026
Merged

Document the release tag ruleset #4

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
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,12 @@ convention:
When the workflows have run in real repositories for a while, `v1` becomes the
first stable line.

The ruleset `protect-release-tags` blocks creating, moving and deleting `v*`
tags. Only organisation owners can bypass it, so Actions tokens, apps and
deploy keys cannot change a release. Callers reference workflows by tag, and
the organisation's SHA pinning policy does not cover reusable workflows, so
these tags decide what code runs in every caller.

To publish a fix release on the `v0.1` line:

1. Merge the fix to `main` and wait for a green Self-check.
Expand Down
Loading