mirrors/pikasTech-unidesk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: require provider remote upgrade

Browse Source
This commit is contained in:
Codex
2026-05-05 01:49:05 +00:00
parent f6d0bd1e3b
commit eb6df3ba92
11 changed files with 16 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/e2e.md
+4
View File
@@ -40,3 +40,7 @@ Before claiming delivery, run these checks and keep their JSON output or screens
3. `bun scripts/cli.ts server status`
4. `bun scripts/cli.ts e2e run`
5. a database persistence marker check across at least one CLI-controlled restart
## Provider Upgrade Gate
When delivery explicitly includes upgrading a compute node such as D601 or D518, the automated E2E plan check is not sufficient. The operator must first bootstrap any legacy provider manually if it cannot yet schedule upgrades, then run `provider.upgrade` with `mode: "schedule"` against that Provider ID, confirm the task succeeds, confirm the node reconnects in the public frontend, and finally verify any required `host.ssh` capability with `bun scripts/cli.ts ssh <PROVIDER_ID> hostname`. This schedule check is a node-upgrade gate, not a replacement for the standard public frontend Playwright E2E gate.