rcourtman 4d6935f4fa Restore update-flow coverage as a v6 Playwright spec, retire test-updates workflow ... The Update Integration Tests workflow lost its Go test (tests/integration/api) in the v6 release commit and was reduced to a diagnostic smoke test that duplicated the test-e2e stack boot. Replace it with tests/79-update-flow.spec.ts in the main suite, which runs via test-e2e.yml on the same trigger paths: - stable-channel check returns the mock v99.0.0 release and filters the v99.1.0-rc.1 prerelease (regression guard for the auto-update prerelease bug); rc-channel check surfaces the prerelease - update plan reports honest manual instructions for the docker deployment with readiness attached - apply refuses prerelease download URLs on the stable channel (409) - apply of an unsigned artifact fails closed at SSHSIG verification; a completed update against the unsigned mock artifact would mean the pinned-key trust root was bypassed The old happy-path apply test is intentionally not revived: v6 made SSHSIG verification against the pinned pulse-installer key mandatory, so completing an apply would require shipping the real signing key to the harness or weakening the trust root. mock-github-server now serves v-prefixed asset names and download paths like real Pulse releases (pulse-v99.0.0-linux-amd64.tar.gz); the in-app updater only recognizes v-prefixed versions in download URLs, so the old unprefixed shape made every apply fail validation before reaching the paths under test. Unknown non-tarball sidecar files (e.g. .sshsig) now 404 instead of falling back to tarball bytes. The spec self-skips when the update check is not served by the mock server, so managed-local-backend runs are unaffected.		2026-07-08 01:06:00 +01:00
..
integration	Restore update-flow coverage as a v6 Playwright spec, retire test-updates workflow	2026-07-08 01:06:00 +01:00
migration	Clear all errcheck and gofmt violations so make lint gates on real findings	2026-06-09 21:42:21 +01:00