ci: GitHub Release pipeline on version tags - #9
Merged
Merged
Conversation
Push a v* tag to build the Windows onedir bundle with PyInstaller and publish a GitHub Release. Runs the test suite as a gate first, zips dist\Screamer with a SHA256 checksum, and uses the gh CLI to create the release with auto-generated notes. Hyphenated tags publish as pre-releases.
Add a Releases section to the README explaining the tag-to-release flow, and check in the implementation plan for the release pipeline.
KristianP26
force-pushed
the
ci/release-pipeline
branch
from
June 2, 2026 11:07
510958a to
f7c352b
Compare
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
2 participants
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.
What
Adds an automated GitHub Release pipeline. Pushing a
v*tag builds the Windows executable and publishes a release with the artifact attached — no manual build/upload steps.How
New workflow
.github/workflows/release.yml(triggered onv*tags):ci.yml(QT_QPA_PLATFORM=offscreen); a broken build never ships.PyInstaller --noconfirm --clean screamer.spec, mirroringbuild_windows.ps1.dist\ScreamerintoScreamer-<tag>-windows-x64.zip+ a.sha256checksum.gh release createwith auto-generated notes. Built-inghCLI, no third-party action (matches the project's minimal-dependency ethos). Hyphenated tags (v1.0.0-rc1) publish as pre-releases.permissions: contents: writeis scoped to this workflow for release creation.Docs
docs/RELEASE_PIPELINE_PLAN.mdchecks in the implementation plan.Notes
End-to-end can only be verified by pushing a real tag; the build/test steps mirror the already-green
ci.ymlandbuild_windows.ps1, and the YAML was validated locally.