@raybase/create 0.3.20 → 0.3.22

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@raybase/create",
3
- "version": "0.3.20",
3
+ "version": "0.3.22",
4
4
  "description": "Scaffold secure internal apps powered by Raybase.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -171,7 +171,13 @@ host's code sets `props`; a dispatcher must never copy request data into
171
171
  them. `POST /__raybase/host/backup` then takes one backup and answers `200 {
172
172
  key, bytes, date }`, `409 { error, code: "BACKUP_NOT_CONFIGURED" }` when
173
173
  backups are off, unbound or keyless, or `503 { error, code }` when it fails;
174
- without the prop the address answers as an unknown one. A host backup counts
174
+ without the prop the address answers as an unknown one. With
175
+ `RAYBASE_HOST_VERSION` set (the host's own name for the uploaded version, 1
176
+ to 128 visible ASCII characters, no spaces), every door answer echoes it
177
+ unchanged in the `raybase-host-version` header and as `hostVersion` in the
178
+ body, so a host can tell the new version's answer from that of the version
179
+ still serving; any other value makes every door answer `500
180
+ HOST_VERSION_INVALID`, and takes no backup. A host backup counts
175
181
  toward `RAYBASE_BACKUPS_RETAIN` with the nightly and admin ones (trigger
176
182
  `"host"`, audit `database.backup.host`). Keep `isRaybaseHostRequest(request,
177
183
  ctx)` in the worker entry, ahead of the framework, as the templates have it;