RunicGateway/installer
3
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Compare commits

merge into: RunicGateway:edge
Branches Tags
RunicGateway:main RunicGateway:feat/bundle-branch-url RunicGateway:fix/release-tag-only-installer RunicGateway:ci/bundle-require-aarch64 RunicGateway:bundles RunicGateway:edge
...
pull from: RunicGateway:main
Branches Tags
RunicGateway:feat/bundle-branch-url RunicGateway:fix/release-tag-only-installer RunicGateway:ci/bundle-require-aarch64 RunicGateway:bundles RunicGateway:edge RunicGateway:main

2 Commits
edge ... main

Author SHA1 Message Date
Colby Whitlock
ae53546446 Merge pull request 'ci(bundle): recognize a linux-aarch64 link asset' (#9) from ci/bundle-aarch64-key into main
Some checks failed
sync-project-tree / sync (push) Successful in 6s
Details
Release installer / release (push) Successful in -32s
Details
Compose bundle / compose (push) Failing after 21s
Details 
Reviewed-on: #9
Reviewed-by: Colby Whitlock <whitlocktech@gmail.com>
 2026-08-05 17:51:06 +00:00
wtclaude
fd59a74912 ci(bundle): recognize a linux-aarch64 link asset
All checks were successful
PR Checks / rust-gates (pull_request) Successful in 5s
Details 
Step 1 of PLAN.md §5.2's four, and it has to be first. Two rules in this
job are strict in opposite directions: an unrecognized link asset name
fails the run, and a missing REQUIRED platform key fails it too. So the
name must be taught before the release that carries it, and the key can
only be required after one exists -- requiring it first would fail every
bundle for as long as the gap lasts.

This is therefore the mapping only. linux-aarch64 is not in REQUIRED
yet; step 3 promotes it once a link release actually ships the binary,
after which a dropped target reddens CI instead of vanishing silently
from every bundle.

The compose step needed no change: it builds the asset map from the
platform TSV, so a third key costs it nothing.

Edited on `main` and deliberately not on `edge`. The compose job runs
from `main`, and leaving `edge`'s copy untouched means the eventual
cutover merge has nothing to conflict over.

Co-Authored-By: Claude <noreply@anthropic.com>
 2026-08-05 05:22:59 -05:00
2 changed files with 15 additions and 3 deletions
Expand all files Collapse all files

14
.gitea/workflows/bundle.yml
View File

@@ -173,13 +173,23 @@ jobs:
# Map link's binaries onto platform keys. The pattern is asserted, not # Map link's binaries onto platform keys. The pattern is asserted, not
# assumed: an unrecognized asset name is a hard failure so that adding # assumed: an unrecognized asset name is a hard failure so that adding
# a target to link's release.yml (aarch64, macOS) surfaces here as a # a target to link's release.yml (macOS, a Windows arm64) surfaces here
# red run, rather than being silently dropped from every bundle. # as a red run, rather than being silently dropped from every bundle.
#
# linux-aarch64 is recognized here BEFORE link publishes one
# (PLAN.md §5.2, step 1 of 4). That order is forced by the two rules
# below being strict in opposite directions: an unknown name fails the
# run, and a missing REQUIRED key fails it too. So the name has to be
# taught before the release that carries it, and the key can only be
# required after — requiring it first would fail every bundle for as
# long as the gap lasts. Step 3 promotes it into REQUIRED once a link
# release actually ships the binary.
: > work/link-platforms.tsv : > work/link-platforms.tsv
while IFS="$(printf '\t')" read -r NAME URL; do while IFS="$(printf '\t')" read -r NAME URL; do
[ -n "$NAME" ] || continue [ -n "$NAME" ] || continue
case "$NAME" in case "$NAME" in
*-linux-x86_64) PLAT=linux-x86_64 ;; *-linux-x86_64) PLAT=linux-x86_64 ;;
*-linux-aarch64) PLAT=linux-aarch64 ;;
*-windows-x86_64.exe) PLAT=windows-x86_64 ;; *-windows-x86_64.exe) PLAT=windows-x86_64 ;;
*) fail "unrecognized link asset '${NAME}' — bundle.yml does not know what platform to file it under. Teach it this name or the bundle would silently omit the asset." ;; *) fail "unrecognized link asset '${NAME}' — bundle.yml does not know what platform to file it under. Teach it this name or the bundle would silently omit the asset." ;;
esac esac

4
bundles/README.md
View File

@@ -56,9 +56,11 @@ protocol) or to either component's release version. All three move independently
"tag": "v1.1.0", "tag": "v1.1.0",
"version": "1.1.0", "version": "1.1.0",
"protocol": 3, "protocol": 3,
"assets": { // per-platform: the installer runs on both "assets": { // per-platform: the installer runs on each
"linux-x86_64": { "name": "…", "url": "…", "sha256": "…" }, "linux-x86_64": { "name": "…", "url": "…", "sha256": "…" },
"windows-x86_64": { "name": "…", "url": "…", "sha256": "…" } "windows-x86_64": { "name": "…", "url": "…", "sha256": "…" }
// "linux-aarch64" joins these from link's first release built for it;
// bundle.yml already knows the name (PLAN.md §5.2)
} }
}, },