A node's worker label is worker, so a device is only a paired one
- NodeDef `device`/`device_policy` become `worker`/`worker_policy`, the issue `ignored_device` becomes `ignored_worker`, and the SDK's `@node` takes `worker=` and `worker_policy=` - FlowStore._migrate renames the keys in published and draft documents once, bumping their version; a queued run's `needs` reads the old key - placement passes the label as `label`, client regenerated - docs: worker placement wording, MCP issuer without DOMAIN, device rows in the CLI data directory and the API table, device links in compose comments Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
f8011d2a8a
commit
a9d453c9d9
@@ -22,10 +22,9 @@ export const firstSuperuserPassword = getEnvVar("FIRST_SUPERUSER_PASSWORD")
|
||||
* The two origins a run talks to: the app in the browser, and the API for the
|
||||
* setup and teardown around a spec.
|
||||
*
|
||||
* Deliberately *not* taken from `VITE_API_URL`, even though `../../.env` above
|
||||
* has one. That variable belongs to the app build, and in a checkout configured
|
||||
* for a deployment it names the deployment — so a suite reading it would drive
|
||||
* a browser at the local stack while sending its `DELETE`s to the live
|
||||
* Deliberately *not* taken from `../../.env` above, which in a checkout
|
||||
* configured for a deployment names the deployment. A suite reading it would
|
||||
* drive a browser at the local stack while sending its `DELETE`s to the live
|
||||
* instance. Both origins come from the same place instead: whatever the browser
|
||||
* is pointed at is what teardown may write to.
|
||||
*/
|
||||
|
||||
Reference in New Issue
Block a user