workflow 4.8.5 → 4.8.7
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.
|
@@ -101,6 +101,18 @@ The `deploymentId` option is currently a Vercel-specific feature. Other Worlds m
|
|
|
101
101
|
In Worlds without atomic, immutable deployments (such as local development or self-hosted Postgres), there is no notion of multiple deployments to resolve between, so `deploymentId: "latest"` has no effect: the SDK logs a warning and the run targets the current deployment. This means a workflow that opts into `"latest"` on Vercel still runs unchanged in local development.
|
|
102
102
|
</Callout>
|
|
103
103
|
|
|
104
|
+
<Callout type="info">
|
|
105
|
+
Resolving `"latest"` is the one `start()` path that calls the Vercel API, so it
|
|
106
|
+
needs an identity that can see the calling deployment. Inside a Vercel
|
|
107
|
+
deployment the SDK authenticates with the deployment's own OIDC token, which
|
|
108
|
+
carries the owning team, and this takes precedence over a `VERCEL_TOKEN` set in
|
|
109
|
+
the function's environment. A `VERCEL_TOKEN` belongs to a *user* and carries no
|
|
110
|
+
team, so authenticating with it scopes the lookup to that user's default team
|
|
111
|
+
and fails with a 404 whenever that is not the team that owns the deployment.
|
|
112
|
+
Outside a deployment (CLI, CI, the dashboard) `VERCEL_TOKEN` is still used;
|
|
113
|
+
configure the World's `teamId` so the request is scoped explicitly.
|
|
114
|
+
</Callout>
|
|
115
|
+
|
|
104
116
|
<Callout type="warn">
|
|
105
117
|
When using `deploymentId: "latest"`, the workflow run will execute on a potentially different deployment than the one calling `start()`. Be mindful of forward and backward compatibility:
|
|
106
118
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "workflow",
|
|
3
|
-
"version": "4.8.
|
|
3
|
+
"version": "4.8.7",
|
|
4
4
|
"description": "Workflow SDK - Build durable, resilient, and observable workflows",
|
|
5
5
|
"main": "dist/typescript-plugin.cjs",
|
|
6
6
|
"type": "module",
|
|
@@ -57,18 +57,18 @@
|
|
|
57
57
|
},
|
|
58
58
|
"dependencies": {
|
|
59
59
|
"ms": "2.1.3",
|
|
60
|
-
"@workflow/astro": "4.0.
|
|
61
|
-
"@workflow/cli": "4.3.
|
|
62
|
-
"@workflow/core": "4.8.
|
|
60
|
+
"@workflow/astro": "4.0.22",
|
|
61
|
+
"@workflow/cli": "4.3.11",
|
|
62
|
+
"@workflow/core": "4.8.7",
|
|
63
63
|
"@workflow/errors": "4.2.1",
|
|
64
64
|
"@workflow/typescript-plugin": "4.0.3",
|
|
65
65
|
"@workflow/utils": "4.1.4",
|
|
66
|
-
"@workflow/next": "4.1.
|
|
67
|
-
"@workflow/nest": "4.0.
|
|
68
|
-
"@workflow/nitro": "4.1.
|
|
69
|
-
"@workflow/nuxt": "4.0.
|
|
70
|
-
"@workflow/sveltekit": "4.0.
|
|
71
|
-
"@workflow/rollup": "4.0.
|
|
66
|
+
"@workflow/next": "4.1.11",
|
|
67
|
+
"@workflow/nest": "4.0.23",
|
|
68
|
+
"@workflow/nitro": "4.1.13",
|
|
69
|
+
"@workflow/nuxt": "4.0.23",
|
|
70
|
+
"@workflow/sveltekit": "4.0.22",
|
|
71
|
+
"@workflow/rollup": "4.0.22"
|
|
72
72
|
},
|
|
73
73
|
"devDependencies": {
|
|
74
74
|
"@types/ms": "2.1.0",
|