Skip to content

Commit dd0cd5f

Browse files
Brooooooklynclaude
andcommitted
docs(platform): add upgrade order and sandbox token steps
Operators were not told to upgrade the platform before the team updates the CLI, although a newer CLI refuses an older platform. They were also not told that a runtime token from an older setup link lacks the Containers and Cloudchamber permissions that sandbox apps need, which an upgrade does not add. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 parent 813a714 commit dd0cd5f

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

‎docs/guide/platform/installation/maintenance.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,9 @@ Repair recreates missing infrastructure that the installer owns. It does not res
100100

101101
### Upgrade the platform
102102

103-
Keep the platform runtime current when updating the Void CLI.
103+
Keep the platform runtime current when updating the Void CLI. Upgrade the platform before your team updates its CLI: a newer CLI refuses to work with an older platform and asks for `void platform upgrade`. Install the new CLI on the administrator's machine, run the upgrade below, then have the team update.
104+
105+
If the platform will deploy apps that use `void/sandbox`, its runtime token needs **Account → Containers → Edit** and **Account → Cloudchamber → Edit**. A token made from an older setup link may lack them, and an upgrade does not add them. Edit the token in the Cloudflare dashboard, or set `VOID_PLATFORM_RUNTIME_CLOUDFLARE_API_TOKEN` to a new token when you upgrade. See [Cloudflare API Tokens](/guide/platform/installation/credentials#runtime-token-permissions).
104106

105107
Use the installed CLI's packaged runtime to upgrade:
106108

0 commit comments

Comments
 (0)