Skip to content

docs(release): say that CI runs on the release PR #46

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
StefanoGuerrini merged 2 commits into from
Oct 15, 2026
Merged

docs(release): say that CI runs on the release PR #46

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6824aa6
docs(release): say that CI runs on the release PR
StefanoGuerrini Oct 15, 2026
813ca3c
docs(release): say it more simply
StefanoGuerrini Oct 15, 2026
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
5 changes: 3 additions & 2 deletions docs/contributing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,8 +88,9 @@ To publish an existing tag again, run the Release workflow by hand from

### If the checks fail after the release PR is merged

The release PR runs no CI, so its checks first run after the merge. If they
fail, `main` already has the new version, but there is no tag, and the
The release PR runs CI like any other PR. After you merge it, the release
run checks the code again before it tags and publishes. If that check
fails, `main` already has the new version, but there is no tag, and the
merged release PR keeps the `autorelease: pending` label, which blocks the
next release PR. To recover:

Expand Down
Loading