v7.0.0

Breaking (edge functions only)

• Every function is named by an explicit uuid. Each entry in a functions manifest needs a uuid; 6.x derived one from id when it was missing. quant functions now checks the whole manifest, and that every file exists, before the first upload, and names each problem:

  quant/edge-functions.json is not a valid function manifest:
    Entry 1 (quant/edge-functions/api.js): uuid is required
  

• quant function, quant auth and quant filter require <uuid>. Without one, 6.x created a new function on every run. Output is now Deployed <kind> [<uuid>].
• The manifest is checked against the full schema, the same check the Quant portal uses: type is function, edge, auth or filter (lowercase), description is not blank, uuid and id are unique, every entry is an object. UUIDs are checked for shape only (8-4-4-4-12 hex), so existing UUIDs with any version digit keep working.

New

• quant functions-add <manifest> <path> --description <text> [--type function|auth|filter] [--id <slug>] adds an entry with a new UUID. It uploads nothing, creates the manifest (and its directory) if needed, and prints only the UUID.

  quant functions-add quant/edge-functions.json quant/edge-functions/api.js --description "API" --id my-api

• quant rules --functions validates the functions manifest the same way and resolves function_ref to the entry's uuid.

Upgrading from 6.x

To keep a function 6.x deployed by id, put its UUID in the entry: copy it from the dashboard (Compute > Edge Functions), or recompute it with the command in the README ("Upgrading from 6.x to 7.0.0").

deploy-action v6 pins CLI 6.3.0 and is not affected. deploy-action v7 will use this release.