Updates · Starwisp

The license window #

Your purchase includes 12 months of updates from the date it was issued. Your key shows the date:

npx starwisp license LW1.your-key-here

It prints updates until <date> and whether updates are active or ended.

Your install never stops working. If the window ends, the console, your repos and your apps keep running exactly as they are, forever.
After the date, the update service refuses releases published after that date, and shows a renewal link. Releases published before the date stay available to you.
Renewing adds 12 months and gives you a new key. It is a separate purchase from the site. If you lose your key, use https://getstarwisp.com/retrieve-key.
If you keep an old release file, you may keep using that version.

Your license is saved for updates #

The Update button runs a workflow in your repository, and that workflow needs your license key. The installer saves it for you in github.com/<org>/factory: the Actions secret STARWISP_LICENSE (your whole key) and the variable STARWISP_UPDATE_URL (the update service address, default https://api.getstarwisp.com; it must be https). The Setup page shows a row Updates: license saved that turns green when both are there.

Only the update workflow reads the secret.

If the row says something is missing (for example you installed an earlier build), run npx starwisp init --org <org> again; it is safe to repeat and only does what is missing. Or add them by hand: open github.com/<org>/factory → Settings → Secrets and variables → Actions, add a secret named STARWISP_LICENSE with the whole key from your purchase email (it starts with LW1.), and a variable named STARWISP_UPDATE_URL.

The pull request is opened with a short-lived token from your Starwisp GitHub App, which needs Contents, Pull requests and Workflows read and write (the install asked for these).

How updates arrive #

Banner. When a newer release exists, the console shows Update available: vX.Y on Home and Settings, with the changelog. The check reads a public list of versions, dates and changelogs; nothing about you is sent. Settings → Updates → Check for updates turns it off (it is on by default). The same tab shows your installed version, which is the file .factory/VERSION in your repo.
Click Update. The console starts the factory update workflow in your GitHub Actions. It presents your license to the update service over https, gets a short-lived download, and checks the file's sha256 before it uses it. No AI model runs in it.
Update pull request. A second job, which never sees your license, applies the release on a branch named starwisp/update-vX.Y.Z and opens a pull request into main. The body is the changelog entry for that version and says how many of your own files were left alone.
You review and merge. Nothing changes until you merge. The console is redeployed by your normal Cloudflare build when main changes.

If your update window has ended before that release came out, the run says so, names the date and the newest release you can still get, shows the renewal link, and opens no pull request. Your install keeps working.

The workflow only ever runs when you click Update (or start it yourself from the Actions tab). Nothing schedules it.

Your settings are safe #

The files listed in .factory/customer-owned.json (your identity, budget, pipeline and studio settings, memory, ledger, and everything under .factory/local/, including prompt overrides, the Setup page's checkboxes and the update settings) are never overwritten by an update. If a new version needs a settings change, the pull request shows it in the diff.

Prompt customisation goes in an override file for the stage under .factory/local/prompts/, layered on the shipped prompt, so a new release's prompt text does not erase it. Nothing is deleted by an update.

Conflicts happen only if you edited a file that Starwisp ships (for example a workflow). Review those files in the pull request as you would any change.

Undo an update #

Not merged yet: close the pull request (and delete its branch if you want to run the update again).
Already merged: revert the merge commit on GitHub (the Revert button on the merged pull request). The previous console version also stays in Cloudflare's version history.

If the update run fails #

Open the run from the console's "Watch the run" link. Each failure is a plain sentence:

It says	Do this
No license is saved in this repository	Add the `STARWISP_LICENSE` secret (see "Your license is saved for updates" above).
The update service did not accept the license	Paste the whole key again. If it keeps failing, use https://getstarwisp.com/retrieve-key.
This license has been revoked	Contact support if you think that is a mistake.
Your license covers updates until …	Renew, then run again. Or choose an older version by starting the workflow from the Actions tab and typing its version number.
The branch `starwisp/update-vX.Y.Z` already exists	Merge or close the earlier pull request, delete the branch, then run again.
The update service could not give a download	Try again in a few minutes.

If the update service is down #

Your install keeps running. Try again later, or use the manual download link in your purchase email.

Plain-text version of this page: /docs/updates.md. This page is copied from the product's own docs, so it matches the release you install.

Next: Troubleshooting