ci: add rolling latest release workflow - #18
Merged
Conversation
On every push to `main`, build the 6 cross-compiled release targets and overwrite the assets on the `latest` GitHub Release — a rolling snapshot (prerelease, make_latest:false) using the flutter-starter releases/tag/latest pattern (single softprops/action-gh-release step, tag_name: latest). Mirrors release.yml: same 6-target build matrix, the cargo-deny/cargo-audit supply-chain gate, and the install.sh/install.ps1 lint gates, all blocking publish. The tagged v* release flow (release.yml) is untouched.
hmziqrs
approved these changes
Jul 29, 2026
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
On every push to
main, build the 6 cross-compiled release targets and overwrite the assets on thelatestGitHub Release — a rolling snapshot refreshed every commit. Same pattern ashmziqrs/flutter-starter'sreleases/tag/latest.How
A single
softprops/action-gh-releasestep withtag_name: latest,prerelease: true,make_latest: false:latestis resolved by tag name; same-named assets are replaced each run (the "overwrite"), so the release stays a single object — no duplicates.prerelease+make_latest: falsekeep stablev*releases holding the green Latest badge; this snapshot lives at/releases/download/latest/....Jobs (mirror
release.yml, no new patterns):build— the same 6-target matrix (linux musl x86_64/aarch64, macOS x86_64/aarch64, windows msvc x86_64/aarch64).supply-chain—cargo-deny+cargo-auditgate.lint-scripts/lint-scripts-windows— parse-checkinstall.sh/install.ps1before they ship.publish— assembleSHA256SUMS, thenaction-gh-releaseto thelatesttag.release.yml(taggedv*releases) is untouched.Branch note
Trigger is
main— this repo's default branch (nomasterexists onfreeoxide/tunnel).flutter-starterusesmasterbecause its default branch ismaster; same pattern, different branch name.Verified
release.yml).release.yml); matrix/SHAs/packaging confirmed byte-identical torelease.yml.After merge
First push to
main(or a manualworkflow_dispatch) creates thelatestrelease with the 6 archives + installers +SHA256SUMS. A subsequent push replaces (not duplicates) the assets.