bvandeusenandClaude Opus 5.5
f16224b07c
Android / Build, or is the channel already serving this? (push) Successful in 3s
CI & Build / Python lint (push) Successful in 2s
CI & Build / Build now, or wait for Android? (push) Successful in 2s
Desktop (Tauri) / Build, or is the channel already serving this? (push) Successful in 2s
CI & Build / Web typecheck and unit tests (push) Successful in 12s
CI & Build / Python tests (push) Successful in 23s
Android / Core and FFI clippy and tests (push) Successful in 51s
CI & Build / integration (push) Successful in 1m49s
CI & Build / Build & push image (push) Skipped
Desktop (Tauri) / Web tests, clippy, Rust tests and rustfmt (push) Successful in 2m20s
Desktop (Tauri) / Windows installer (cross-compiled) (push) Successful in 3m6s
Desktop (Tauri) / Tauri desktop (Linux) (push) Successful in 3m46s
Desktop (Tauri) / Update manifest (push) Successful in 3s
Android / Kotlin + Rust (APK) (push) Successful in 8m31s
Android / Build the server image (push) Successful in 1s
#6225 "Comment standard sweep: root, config, CI workflows, docs and packaging", milestone 546 "Bring the repo to the comment standard (rule 32) and compose defaults (rule 198)". - README restructured in newcomer order: what it is, quick start, configuration, setup pitfalls, updating and backups, features, troubleshooting, development, licence. Its quick-start compose carries no restart policy. - Dockerfile and .env.example trimmed to one or two lines per setting. - Workflows, packaging scripts and docs lose issue, run, note, rule and milestone references and their history narration. Comments that still described path filters and "step 6" as future work now state what the workflows do. - ci-requirements.md rewritten against the current workflows. It said the build gated on typecheck and lint only, the integration lane did not gate, a v* tag published :latest, and ci-tauri lacked bsdtar and zstd; none of those is true now (the last checked against run 9630's log). - Echo strings in guard-forward.sh and version.sh drop their note citations; every string a test asserts on is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
29 lines
1.1 KiB
Bash
29 lines
1.1 KiB
Bash
#!/usr/bin/env sh
|
|
#
|
|
# The release tag that holds a channel's builds.
|
|
#
|
|
# channel-tag.sh <dev|stable>
|
|
#
|
|
# A channel and its release tag are two different names, and for `dev` they differ.
|
|
# The channel is what a person picks and sees (`install.sh --channel dev`, the app's
|
|
# settings); the tag is where CI publishes and where every reader fetches from.
|
|
#
|
|
# A tag named `dev` would shadow the branch named `dev`: once a clone had fetched
|
|
# tags, `git push origin dev` would fail with "src refspec dev matches more than
|
|
# one". So the dev channel's tag is `dev-rolling`. Never spell a channel tag like a
|
|
# branch — tests/test_channel_tag.py fails if one is.
|
|
#
|
|
# The ONE mapping CI reads. Two copies exist because their readers cannot run this:
|
|
# `desktop/src-tauri/src/update.rs` (compiled into the app) and
|
|
# `desktop/packaging/install.sh` (fetched alone through a pipe). Change all three.
|
|
set -eu
|
|
|
|
case "${1:-}" in
|
|
dev) echo dev-rolling ;;
|
|
stable) echo stable ;;
|
|
*)
|
|
echo "channel-tag.sh: unknown channel '${1:-}' (expected dev or stable)" >&2
|
|
exit 2
|
|
;;
|
|
esac
|