workflow 5.0.0-beta.17 → 5.0.0-beta.19
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.
|
@@ -103,6 +103,8 @@ const run = await start(myWorkflow, ["arg1", "arg2"], { // [!code highlight]
|
|
|
103
103
|
|
|
104
104
|
<Callout type="info">
|
|
105
105
|
The `deploymentId` option is currently a Vercel-specific feature. Other Worlds may implement this option differently to match their own deployment runtimes, and the World spec may rename it from `deploymentId` to `version` in a future SDK version. On Vercel, `"latest"` resolves to the most recent deployment matching your current environment — the same production target for production deployments, or the same git branch for preview deployments.
|
|
106
|
+
|
|
107
|
+
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.
|
|
106
108
|
</Callout>
|
|
107
109
|
|
|
108
110
|
<Callout type="warn">
|
|
@@ -42,6 +42,19 @@ npx workflow inspect runs --web
|
|
|
42
42
|
|
|
43
43
|
|
|
44
44
|
|
|
45
|
+
To share a link to a specific run without opening a browser, use the `--url`
|
|
46
|
+
flag. It prints the dashboard deep link to stdout and exits (no browser, no
|
|
47
|
+
local server) — useful for scripts, PR comments, or automation. Add `--json` to
|
|
48
|
+
get `{ "url": "..." }`.
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
# Print the deep-link URL for a run (no browser, no server)
|
|
52
|
+
npx workflow inspect run <run_id> --url
|
|
53
|
+
|
|
54
|
+
# Vercel runs: add the backend (and --env preview for preview deployments)
|
|
55
|
+
npx workflow inspect run <run_id> --backend vercel --url
|
|
56
|
+
```
|
|
57
|
+
|
|
45
58
|
## Backends
|
|
46
59
|
|
|
47
60
|
The Workflow SDK CLI can inspect data from any [World](/docs/deploying). By default, it inspects data in your local development environment. For example, if you are using Next.js to develop workflows locally, the
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "workflow",
|
|
3
|
-
"version": "5.0.0-beta.
|
|
3
|
+
"version": "5.0.0-beta.19",
|
|
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": "5.0.0-beta.
|
|
61
|
-
"@workflow/cli": "5.0.0-beta.
|
|
62
|
-
"@workflow/core": "5.0.0-beta.
|
|
60
|
+
"@workflow/astro": "5.0.0-beta.19",
|
|
61
|
+
"@workflow/cli": "5.0.0-beta.19",
|
|
62
|
+
"@workflow/core": "5.0.0-beta.19",
|
|
63
63
|
"@workflow/errors": "5.0.0-beta.8",
|
|
64
64
|
"@workflow/typescript-plugin": "5.0.0-beta.4",
|
|
65
65
|
"@workflow/utils": "5.0.0-beta.4",
|
|
66
|
-
"@workflow/next": "5.0.0-beta.
|
|
67
|
-
"@workflow/nest": "5.0.0-beta.
|
|
68
|
-
"@workflow/nitro": "5.0.0-beta.
|
|
69
|
-
"@workflow/nuxt": "5.0.0-beta.
|
|
70
|
-
"@workflow/sveltekit": "5.0.0-beta.
|
|
71
|
-
"@workflow/rollup": "5.0.0-beta.
|
|
66
|
+
"@workflow/next": "5.0.0-beta.19",
|
|
67
|
+
"@workflow/nest": "5.0.0-beta.19",
|
|
68
|
+
"@workflow/nitro": "5.0.0-beta.19",
|
|
69
|
+
"@workflow/nuxt": "5.0.0-beta.19",
|
|
70
|
+
"@workflow/sveltekit": "5.0.0-beta.19",
|
|
71
|
+
"@workflow/rollup": "5.0.0-beta.19"
|
|
72
72
|
},
|
|
73
73
|
"devDependencies": {
|
|
74
74
|
"@types/ms": "2.1.0",
|