What this changes
Maintainers propose a Beta straight from a pre-alpha build that passed its tests. There is no Promote to Alpha run and no alpha approval any more, and nothing reaches installed clients before the beta approval.
- Pre-alpha (
prealpha.yml) now also runs the app tests on every build:ios-app.yml(three macOS jobs: PokiCore and loopback tests, the in-process checks, the simulator smoke test and screenshots, the app unit tests, Poki's agent end to end) and Poki Setup's core tests on Linux. They do not hold up the pre-alpha. They start after the build, and only the build job waits for the previous build, so tests never delay the next merge. A manual run of Pre-alpha keeps a singlePoki-unsignedartifact (skip_ipa_upload). - Propose promotion > beta takes a pre-alpha tag, the merge commit it was built from, or nothing (the build on
app-prealpha-latest). It refuses a build whose Pre-alpha run failed or is still running, whose run never ran the tests, or whose artifact has expired, and links the run. A newdry_runinput prints the promotion and opens no PR. A run from any branch other thanmainbehaves the same way. - Publish promotion publishes nothing before the
betaapproval. Older Poki and Poki Setup install whatever the Alpha releases carry, on every channel. So after the approval, the onepublishjob puts the same build onapp-X.Y.Z-alpha.N,app-alpha-latestandios-alpha-latest, then publishes the Beta. Both come from the Pre-alpha run's artifact, downloaded once; the Beta's files are gathered in an empty folder, not next to the Alpha's. The repository owner tests the build on a real iPhone before approving. promote-alpha.ymlandpromote-alpha-fast.ymlare removed.docs/release-channels.md,docs/update-sources.md, AGENTS.md and the README line about release channels describe the new flow.- The release plans in
scripts/release/plans/follow the new order, and name the Beta's IPA with its build number as the workflow does. The hand-madeios-beta-X.Y.Z-Nand Alpha-tag releases (publish-compat.sh) move to right after the approval. - Stable, the Gym gate and the
blockerandsoak-overridelabels are unchanged.
How you tested it
-
node --test test/promotion.test.mjs(new, in PR checks). Each case fails onmainor on this PR's first commit, and passes here:- proposing from
app-prealpha-latest; - refusing a commit whose Pre-alpha run failed;
- refusing a run that never ran the tests;
- checking that only a job behind the
betaenvironment writes the Alpha records.
- proposing from
-
actionlintpasses on all workflows.test/publish-compat.test.mjspasses. -
I dispatched Propose promotion as a dry run from this branch:
- Before the tests joined the run, with an empty
from, it resolvedapp-0.4.5-prealpha.1724and opened no PR: https://github.com/JosssphZhou/poki/actions/runs/44253038249 - With the commit
55b04d6, whose Pre-alpha run failed, it was refused and the run was linked: https://github.com/JosssphZhou/poki/actions/runs/44253057030 - With the tests required, the same build 1724 is refused because its run has no test jobs: https://github.com/JosssphZhou/poki/actions/runs/44268103470
- Before the tests joined the run, with an empty
-
Nothing before the approval writes the Alpha records: the only
publish-rolling.sh alphacall is in thepublishjob, which waits for thebetaenvironment, and a test above checks that. As a consequence, simulated withnode scripts/release/first-hop-check.mjs(all three plans pass with--build 1724), Poki 0.3.1 (752) and Poki Setup 0.2.2 (661) keep the release they had on every channel until the approval step. A live before and after comparison needs the first real promotion. -
Not run: a real merged promotion, and a Pre-alpha run with the tests. Both run for the first time after this merges. The job names
app-tests / <job>follow what GitHub reported for the old Promote to Alpha run'sios-tests / <job>. -
Note: the app tests failed in the last three Promote to Alpha runs (for example https://github.com/JosssphZhou/poki/actions/runs/43577698333). Until they pass on
main, no build can be proposed for Beta. #481 deals with the timing failures behind them and should merge first. -
I removed passcodes, tokens, and private screen contents from this PR.
-
I release this contribution under the AGPL-3.0-only license.
🤖 Generated with Claude Code