ci(release): build Router downloads when a release is published - #221
Merged
Merged
Conversation
Add a main-only manual entry point that builds and verifies both Linux archives before creating the immutable source tag and populated draft. Preserve tag-push releases, serialize publication, and reject conflicting tags or published assets. Document the browser release steps and link the draft from the run summary. [design:WF-ADR-0069]
Replace manual dispatch and draft creation with the published release event. Attach verified native downloads automatically, retaining identical assets on retry and rejecting changed tags or conflicting downloads. Document the public build interval and requirement for post-publication asset uploads. [design:WF-ADR-0069]
tcballard
changed the title
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.
Publishing a Router release should start its build automatically. This replaces the tag-push pipeline with
release: types: [published]; there is no manual Run workflow step or automated draft creation.Publish
router-v<VERSION>targeting the merged main commit. GitHub validates the version, notes and source ancestry, builds and smoke-tests x86_64 and aarch64 archives, verifies checksums, then attaches the four downloads to that same release. Desktop releases are ignored. The release page is public while builds run; downloads appear after success.Retries retain byte-identical assets and add missing ones. Conflicting assets and moved tags are rejected; uploads never use clobber. GitHub immutable releases are rejected because they prohibit adding assets after publication. Repository settings are not changed.
Validation: packaging tests and workflow shell parsing pass. Local mocked GitHub/Git checks pass for initial upload, identical retry, conflicting asset, immutable release, and moved tag. Live release-event execution remains to be verified after merge. No release has been published by this PR.
Updates maintainer instructions, changelog and WF-ADR-0069. Once Router 1.1.0 downloads are published and verified, the Omarchy plugin pins can be updated.