mr.zeroandClaude Opus 5
e35a72336a
An installed title's version line now reads `0.1 → 0.3` where the catalog has moved on, so a card answers both questions somebody brings to it: what is installed, and is there anything better. Which version is installed was already recorded — `state.json` has always carried it — what was missing was anywhere to act on it. The card leads with Play (or Open, for a hosted title) and puts the rest behind a ⋮ button: Upgrade, which fetches whatever the catalog now has, and Uninstall. Upgrade stays visible while disabled rather than appearing and disappearing — a menu whose items come and go makes a person hunt for the one they used last time, and greyed out already says "not now". Playing stays the headline even with an upgrade waiting: the build on the disk still runs, and wanting to play it is not the same as wanting to wait for a download. The menu is a `<details>`, so its open state is the DOM's and the keyboard needs no teaching. Closing it on an outside click is the grid's job, not a card's: cards are rebuilt on every render, so a listener per card would be a listener per render. Package names lose their spaces — `WarpEngineClient-2.3.0-arm64.dmg` — because a space in a release asset is a space in every curl, script and shell command that touches it. Set per target rather than globally: nsis and portable would otherwise resolve to the same .exe name and overwrite each other. `productName` is untouched, so the app is still called WarpEngine Client where a person sees it — in the Dock and in /Applications. Tested on a sandbox store by rewriting one state record to claim an older build, which is what the engine actually compares: the window then offered `Upgrade:on` for that title and `Upgrade:off` for the current one, and pressing it took the record from 0.1 to 0.2 with the old payload removed first. The self-test asserts that pairing on every installed card, because a closed menu photographs identically whether or not its items are right. In Hungarian the catalog refresh and the new Upgrade both wanted "Frissítés"; the refresh is an icon with a tooltip, and a tooltip can afford to say *Katalógus frissítése*. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
116 lines
4.9 KiB
Bash
Executable File
116 lines
4.9 KiB
Bash
Executable File
#!/bin/sh
|
|
# Attach built packages to the Gitea release for this tag.
|
|
#
|
|
# The local publisher (scripts/release.sh) drives `tea`, which is logged in
|
|
# interactively on a workstation. CI has no such session: it has a token and curl. The
|
|
# two are deliberately separate scripts rather than one with two ways to authenticate —
|
|
# each is short enough to read in full.
|
|
#
|
|
# scripts/ci-upload.sh every package in dist/
|
|
# scripts/ci-upload.sh dist/one.deb just these
|
|
#
|
|
# Authenticates with the `gitea_token` secret when there is one, and otherwise with the
|
|
# credential Woodpecker gives every step for cloning — so a release needs no secret.
|
|
#
|
|
# Creates the release when the tag has none, with RELEASE_NOTES.md as its body. That is
|
|
# the flow: a `vX.Y.Z` tag starts this pipeline, which publishes the release with the
|
|
# Linux and Windows packages in it, and the macOS package is pushed on top afterwards by
|
|
# `make release` from a Mac.
|
|
set -eu
|
|
|
|
FORGE="${FORGE_API:-https://git.teletypegames.org/api/v1}"
|
|
REPO="${REPO:-${CI_REPO:-}}"
|
|
TAG="${TAG:-${CI_COMMIT_TAG:-}}"
|
|
DIST="${DIST:-dist}"
|
|
NOTES="${NOTES:-RELEASE_NOTES.md}"
|
|
|
|
say() { echo "[ci-upload] $*"; }
|
|
die() { echo "[ci-upload] error: $*" >&2; exit 1; }
|
|
|
|
# Who to be. A `gitea_token` secret wins when there is one; otherwise the credential
|
|
# Woodpecker already hands every step for cloning is used, which is an access token of
|
|
# the repository's owner — so publishing needs no secret of its own. Gitea accepts a
|
|
# personal access token as `token …` and an OAuth one as `Bearer …`, and which of the two
|
|
# this is depends on how Woodpecker was set up, so the scheme is probed once rather than
|
|
# assumed.
|
|
TOKEN="${GITEA_TOKEN:-${CI_NETRC_PASSWORD:-}}"
|
|
[ -n "$TOKEN" ] || die "no credential: set GITEA_TOKEN, or run this where Woodpecker provides CI_NETRC_PASSWORD"
|
|
[ -n "$REPO" ] || die "cannot work out the repository — set REPO=owner/name"
|
|
[ -n "$TAG" ] || die "cannot work out the tag — set TAG=v1.2.3"
|
|
|
|
AUTH=""
|
|
for scheme in token Bearer; do
|
|
if curl -fsS -H "Authorization: $scheme $TOKEN" "$FORGE/user" >/dev/null 2>&1; then
|
|
AUTH="Authorization: $scheme $TOKEN"
|
|
say "authenticated with the $scheme scheme"
|
|
break
|
|
fi
|
|
done
|
|
[ -n "$AUTH" ] || die "the credential was refused by $FORGE — it cannot read /user"
|
|
|
|
api() {
|
|
method="$1"; path="$2"; shift 2
|
|
curl -fsS -X "$method" -H "$AUTH" "$FORGE$path" "$@"
|
|
}
|
|
|
|
# The list lives one path per line in a file and is read with `while IFS= read -r`. The
|
|
# built package names have no spaces in them any more, but a path given on the command
|
|
# line still can — and a single variable looped over with $list splits on the space and
|
|
# uploads nothing, which is a silent way to publish a release with no assets.
|
|
LIST="$(mktemp)"
|
|
trap 'rm -f "$LIST"' EXIT
|
|
if [ "$#" -gt 0 ]; then
|
|
for given in "$@"; do printf '%s\n' "$given"; done > "$LIST"
|
|
else
|
|
# What this pipeline builds. The macOS packages are attached from the Mac that can
|
|
# sign them, so they are not listed here even when they happen to be present.
|
|
find "$DIST" -maxdepth 1 -type f \
|
|
\( -name '*.AppImage' -o -name '*.deb' -o -name '*.exe' \) 2>/dev/null | sort > "$LIST" || true
|
|
fi
|
|
[ -s "$LIST" ] || die "no Linux or Windows packages in $DIST"
|
|
|
|
say "$REPO $TAG"
|
|
|
|
# `curl -f` fails on the 404 a missing release answers, so the lookup is allowed to
|
|
# fail and judged by what came back rather than by its exit status.
|
|
release_id="$(curl -sS -H "$AUTH" "$FORGE/repos/$REPO/releases/tags/$TAG" | jq -r '.id // empty')"
|
|
|
|
if [ -z "$release_id" ]; then
|
|
say "no release for $TAG yet — creating it"
|
|
title="$(jq -r '(.productName // .name) + " " + (.version)' package.json)"
|
|
notes=''
|
|
[ -f "$NOTES" ] && notes="$(cat "$NOTES")"
|
|
# The body goes through jq rather than string concatenation: release notes are
|
|
# markdown with quotes and newlines in them.
|
|
payload="$(jq -n --arg tag "$TAG" --arg title "$title" --arg body "$notes" \
|
|
'{tag_name: $tag, name: $title, body: $body, draft: false, prerelease: false}')"
|
|
release_id="$(api POST "/repos/$REPO/releases" \
|
|
-H 'Content-Type: application/json' -d "$payload" | jq -r '.id // empty')"
|
|
[ -n "$release_id" ] || die "the release for $TAG could not be created"
|
|
else
|
|
say "the release already exists"
|
|
fi
|
|
|
|
while IFS= read -r asset; do
|
|
[ -n "$asset" ] || continue
|
|
[ -f "$asset" ] || die "no such file: $asset"
|
|
name="$(basename "$asset")"
|
|
encoded="$(printf '%s' "$name" | jq -sRr @uri)"
|
|
|
|
# Replace rather than refuse, so re-running a build lands.
|
|
existing="$(api GET "/repos/$REPO/releases/$release_id/assets" |
|
|
jq -r --arg name "$name" '.[] | select(.name == $name) | .id')"
|
|
for id in $existing; do
|
|
say "replacing $name"
|
|
api DELETE "/repos/$REPO/releases/$release_id/assets/$id" >/dev/null
|
|
done
|
|
|
|
say "uploading $name"
|
|
api POST "/repos/$REPO/releases/$release_id/assets?name=$encoded" \
|
|
-F "attachment=@$asset" >/dev/null
|
|
done < "$LIST"
|
|
|
|
say "done:"
|
|
api GET "/repos/$REPO/releases/$release_id" |
|
|
jq -r '.assets[] | " \(.name) \(.size / 1000000 | floor) MB"'
|