ospab 1c291d9c88 fix(release): the second branch is 'beta', not 'pre-release' — was never checkoutable ... scripts/gha.ps1's -Branch ValidateSet accepted 'pre-release' and would `git checkout pre-release` to promote alpha, but no such branch has ever existed in this repo — only `beta` does (confirmed: `git branch -a`, and the existing 0.4.6-beta/0.4.7-beta release history was cut from `beta`). The very first beta release under the new gha.ps1 versioning scheme would have failed outright on the checkout step. This naming mismatch had spread through the whole release surface: - scripts/gha.ps1: -Branch ValidateSet + all internal checks - .github/workflows/release.yml: a dead branch-name check (harmless only because the workflow currently triggers on tag-push, not branch-push) plus two comments - CONTRIBUTING.md / .ru.md: branch-strategy table documented a `pre-release` branch that doesn't exist - README.md / .ru.md and ostp/src/main.rs: the `ostp update -b <name>` CLI help text/docs - scripts/install.sh: the channel match the CLI flag feeds into Renamed all of it to `beta` to match the branch that actually exists. Left scripts/gha.ps1:21's "semver pre-release identifier" alone — that's the generic semver spec term, unrelated to the branch name, and got reverted after a blanket replace briefly clobbered it. Note: install.sh's alpha/beta self-update paths still assume a rolling GitHub release tagged literally "alpha"/"beta" exists, which no gha.ps1 release ever publishes (only versioned tags like v0.4.7-beta.3) - that's a separate, real bug, tracked apart from this rename since fixing it needs either a floating tag from gha.ps1 or an API-query rewrite of install.sh.		2026-07-12 02:12:57 +03:00
..
release.yml	fix(release): the second branch is 'beta', not 'pre-release' — was never checkoutable	2026-07-12 02:12:57 +03:00