Repository navigation
v0.28.1
A copy's settings now stay through a deploy. If you set anything on a self-hosted copy as a Text variable in the dashboard, read this one: it may have been gone since your last deploy. No migration, and the protocol stays at version 26.
Fixed
- Settings made in the dashboard stay through a deploy. Wrangler removes a plain-text variable it does not find in
wrangler.jsoncunlesskeep_varssays otherwise, and ours did not. So every push and everyupdate-copytook away what had been set as a Text variable, without a word.TURNSTILE_SITE_KEYgoing stops the request forms, and email and the legal pages could go the same way. Secrets were not affected, and neither was Gateweave Cloud. (#215) update-copyreadswrangler.jsoncas data. It searched the file's text for a Worker's name and database, so a release that renameddatabase_namecould get through on a copy with default names, and one that changed its own staging database could stop an update for no reason. (#213)
Changed
- The self-hosting guide says to use the Workers Paid plan. It used to say a free account is enough. It also says where the Git account is on the Deploy form, and what to do when GitHub refuses an update's push because a commit carries a private address. (#214, #215)
Upgrading
No migration. After updating, look through the Worker's variables in the dashboard and set again what has gone. A site key missing there means the request forms were not open. A variable taken out of vars in wrangler.jsonc now stays on the Worker until someone removes it in the dashboard.