Skip to content

CI: publish a GitHub Release with both binaries on v* tags - #2

Merged
MrSapps merged 1 commit into
mainfrom
claude/blissful-johnson-1w5a5v
Oct 1, 2026
Merged

MrSapps merged 1 commit into
mainfrom
claude/blissful-johnson-1w5a5v

Conversation

@MrSapps

@MrSapps MrSapps commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Workflow artifacts expire after 90 days. This adds a release job to ci.yml that runs when a tag matching v* is pushed (for example v1.0.0):

  • It waits for the linux and windows jobs to build and pass their tests.
  • It zips their artifacts as cpp_permuter-linux-x64-<tag>.zip and cpp_permuter-windows-x64-<tag>.zip. Each zip holds the binary, the gta2 compile script, the README and the LICENSE.
  • It publishes them in a GitHub Release with generated release notes, using softprops/action-gh-release@v2 and the job's contents: write permission.

Pushes and PRs without a tag run as before. The release job is skipped.

The README now points to the Releases page first, and to the per-run artifacts second.

Not run yet: the job only runs on a tag. To release, merge this and push a tag such as git tag v1.0.0 && git push origin v1.0.0.

🤖 Generated with Claude Code


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MrSapps
MrSapps merged commit b85f2bb into main Oct 1, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants