ostp/scripts
ospab 6bc646c8a5 fix(install): alpha/beta self-update actually finds a real release now
Direct hotfix to master (like the earlier `ostp setup` wizard fix) - users
curl install.sh live from this branch's raw URL for every self-update, so
this can't wait for the normal alpha->beta->master promotion.

Master's install.sh still had the pre-rename "pre-release" branch check
(the alpha->beta rename landed on alpha/beta after this file's last direct
hotfix, never reaching master) AND the deeper bug: ostp update -b alpha/-b
beta tried to download a GitHub Release literally tagged "alpha"/"beta".
No such tag has ever existed - gha.ps1 cuts a fresh VERSIONED tag every
release (v0.4.2-beta.4, v0.4.3-alpha.2, ...) - so -b beta fell through to
the stable-release path entirely unnoticed (silently "succeeding" with the
wrong, older version) while -b alpha 404'd outright.

Now queries the full /releases list (newest first, unlike /releases/latest
which only ever returns the newest non-prerelease) and takes the first
tag_name containing "-alpha"/"-beta". Brings master to parity with alpha's
same fix.
2026-07-21 18:41:26 +03:00
..
build.ps1 0.4.1: per-key junk marker, GUI polish, pre-release pipeline 2026-07-07 16:33:57 +03:00
gha.ps1 fix(release): rename -Switch param to -NewVersion (silently broke channel resolution) 2026-07-10 03:25:26 +03:00
install.ps1 fix(install): setup wizard is a subcommand now, not a --setup flag 2026-07-18 16:49:08 +03:00
install.sh fix(install): alpha/beta self-update actually finds a real release now 2026-07-21 18:41:26 +03:00
test_linux.sh feat: install script v2 — global PATH symlink, /etc/ostp config, legacy path migration 2026-05-17 21:22:01 +03:00