Skip to content

Release workflow: always publish as a pre-release, promote to latest by hand #201

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
drowaudio merged 1 commit into from
Oct 15, 2026
Merged

Release workflow: always publish as a pre-release, promote to latest by hand #201

Show file tree
Hide file tree
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: 4 additions & 2 deletions .github/workflows/build.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -238,8 +238,10 @@ jobs:
uses: softprops/action-gh-release@v2
with:
body_path: CHANGELIST.md
# Tags like v2.0.0-beta1 are pre-releases, so they don't become "latest"
prerelease: ${{ contains(github.ref_name, '-') }}
# Every release is published as a pre-release, so it doesn't become the
# "latest" release (which the download URLs in the docs point at) until
# it's promoted by hand: gh release edit <tag> --prerelease=false --latest
prerelease: true
files: |
CHANGELIST.md/*
pluginval_Linux.zip/*
Expand Down
11 changes: 6 additions & 5 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -605,11 +605,12 @@ Run internal tests via CLI:
3. Commit: `git commit -am "Version X.Y.Z"`
4. Tag: `git tag -a vX.Y.Z -m "X.Y.Z release"`
5. Push: `git push --tags`
6. Once the release binaries are published, bump the `pluginval-version` default
in `validate/action.yml` and `acceptance/action.yml` (and the README tables) to the new tag

A tag with a hyphen (e.g. `v2.0.0-beta1`) is published as a pre-release, so it
doesn't become the "latest" release that the download URLs in the docs point at.
6. The tag build publishes the release as a **pre-release** (whatever the tag), so
it doesn't yet become the "latest" release that the download URLs in the docs
point at. Check it, then promote it by hand:
`gh release edit vX.Y.Z -R Tracktion/pluginval --prerelease=false --latest`
7. Bump the `pluginval-version` default in `validate/action.yml` and
`acceptance/action.yml` (and the README tables) to the new tag

## Common Tasks for AI Assistants

Expand Down
Loading