release: 0.3.11 #191
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task/3933-release-0-3-11-so-sak-and-the-runners-ta"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tracker: #3933
Cuts sak 0.3.11 from master
8c6fed60, so sak and the runners take agy accounts, which serve the Gemini models: #3841 (PR 162,bbc5f00a) runs and signs in agy accounts, and #3847 (PR 183,25e0ce06) hands every harness the run's instructions. It also carries #3897's tests/run.sh (PR 184), #3648's channel ping (PR 185), #3829's flow page (PR 186), #3744's Interactive slot and caffeinate (PR 187), #3803's slot holder check (PR 188), #3782's hand-over versions from VERSION (PR 189) and #3863's hand-over cleanup (PR 190).The branch changes two lines. Since #3782 the hand-over tests take the versions they update to from VERSION, so a release is the version and the README's tarball name:
src/version.sx:VERSION :: "0.3.11";README.md: the tarball namesak-0.3.11-macos-arm64.tar.gzThe branch touches no file under
web/, so it adds or changes no golden.The live sak reports 0.3.10 at
4502843(#3879's merge, PR 182), whose schema head is migration 53. So the first start of 0.3.11 runs migration 54 alone: #3841's rebuild ofaccount,run_requestandsign_inwithagyin their harness checks.Gates at the head
b352964b, on m5:fastgate run 924 passed, andfullgate run 927 passed. Infull, tests/run.sh built 69 tests and ran them all (runner_handover, runner_launchd and runner_view included, their later versions taken from 0.3.11). release.sh wrotedist/sak-0.3.11-{macos-arm64,linux-x86_64,linux-arm64}.tar.gz, step9 passed, the deploy contract passed, the main Playwright config gave 777 passed and 1 skipped, and the runner config gave 10 passed.Deploying (a backup of the live sak.db, a rehearsal of the image on a copy that times the migration,
scripts/deploy_nas.shwith a long--wait, rollback on failure) and Update all follow the merge.