ci: add tag trigger and GitHub Release job#299
Merged
spe-ciellt merged 1 commit intodevelopfrom Feb 28, 2026
Merged
Conversation
Add 'v*' tag trigger to the push event so version tags run the CI pipeline. Add a release job that depends on ci, downloads the built platform packages, and publishes a GitHub Release via softprops/action-gh-release. Tags containing -rc, -alpha, or -beta are automatically marked as pre-release. Release notes will be written manually on GitHub after the release job creates the draft. Removes generate_release_notes to leave the description blank for manual editing. Add release.yml to group auto-generated release notes by existing repo labels: security, bug/fix/drill, enhancement, documentation, Windows/GTK3/GTK4, and a catch-all. Re-enable generate_release_notes in the release job to populate release descriptions automatically. Add draft: true so the GitHub Release is not immediately public after the build completes. Requires manually clicking Publish on GitHub after reviewing artifacts and writing release notes. Artifact filenames from the build use date and short commit hash (e.g. gerbv_2025-12-25_45ac82_(Debian 13).deb). Before publishing to a GitHub Release, rename them to use the version tag instead (e.g. gerbv_v2.11.0-rc.1_(Debian 13).deb). CI artifact naming is unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add 'v*' tag trigger to the push event so version tags run the CI pipeline. Add a release job that depends on ci, downloads the built platform packages, and publishes a GitHub Release via softprops/action-gh-release. Tags containing -rc, -alpha, or -beta are automatically marked as pre-release.
Release notes will be written manually on GitHub after the release job creates the draft. Removes generate_release_notes to leave the description blank for manual editing.
Add release.yml to group auto-generated release notes by existing repo labels: security, bug/fix/drill, enhancement, documentation, Windows/GTK3/GTK4, and a catch-all. Re-enable generate_release_notes in the release job to populate release descriptions automatically.
Add draft: true so the GitHub Release is not immediately public after the build completes. Requires manually clicking Publish on GitHub after reviewing artifacts and writing release notes.
Artifact filenames from the build use date and short commit hash (e.g. gerbv_2025-12-25_45ac82_(Debian 13).deb). Before publishing to a GitHub Release, rename them to use the version tag instead (e.g. gerbv_v2.11.0-rc.1_(Debian 13).deb). CI artifact naming is unchanged.