Files
rich 172c53f46d
build / build (push) Successful in 20s
Build from upstream's latest full release instead of the branch tip
ci-build.sh now defaults to UPSTREAM_REF=latest-release, resolved through
GitHub's releases/latest (which skips pre-releases and drafts); the
keymindCascade tip was 693 commits and 13 pre-releases past
v1.18.0.1-halo-keymind-cascade-dev-03214a16. A branch, tag or commit still
works, and build.env records UPSTREAM_TAG.

The workflow skips the build when the newest release's upstream commit isn't
an ancestor of the new one (publish-release.py --behind), so going from the
pre-release-based builds back to 03214a16 doesn't make -hz.U go backwards.
Builds resume once upstream publishes a full release past c12050f.
2026-11-05 21:18:11 -05:00
..