Repository navigation
Update all examples to workflow 5.0.1 - #52
Conversation
`getWorld()` returns a Promise<World> as of v5, so `getWorld().start?.()` no longer type-checks (and silently no-ops at runtime). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The example has no build script, so the earlier sweep never exercised it. Running it surfaced four v5 changes: - `flow.js` / `webhook.js` are now `flow.mjs` / `webhook.mjs`, ESM with named exports only, so the default imports resolved to undefined. - `step.js` became `__step_registrations.mjs`, an internal module that `flow.mjs` imports. The `POST /.well-known/workflow/v1/step` route is deleted rather than repointed. - The SWC plugin's `client` mode was removed and merged into `step`. - `@swc/core` and `@workflow/swc-plugin` were never declared. They resolved through bun's flat node_modules; under pnpm they do not. Verified end to end: the run starts, all steps execute, and the webhook link is issued. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The nitro build failed with "replacement content must be a string" from rollup's ImportExpression.render. It is a rollup 4.53.3 bug, reproducible only when @vercel/oidc 3.0.5 and 3.8.2 are both in the tree: rollup renders the dynamic imports in oidc 3.0.5's get-vercel-oidc-token.js while their target modules are assigned to no chunk, so a Module object reaches MagicString.overwrite instead of a string. The stale lockfile was holding rollup at 4.53.3 and @vercel/sandbox at 1.0.4 (whose ^3.0.5 oidc range was pinned to literally 3.0.5). Raising the rollup floor to ^4.62.4 encodes the actual constraint; the regenerated lockfile also floats sandbox to 1.10.2, which drops the 3.0.5 copy. The lockfile was regenerated against a scratch pnpm store so its tarball entries carry integrity hashes, which makes it installable again. No Workflow SDK change is involved: the example needs no source changes for v5, and relaxing world-vercel's @vercel/oidc pin does not fix it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Bumps workflow, @workflow/world-local, @workflow/world-postgres and @workflow/swc-plugin to 5.0.0 and refreshes lockfiles. @workflow/ai is pinned to 5.0.0-beta.16: the 5.0.0 version on npm is a stale publish that peers on workflow ^4.3.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pnpm 11 ignores the package.json pnpm field and dropped the overrides block, breaking frozen installs on Vercel (pnpm 10). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- hono, ffmpeg-processing: bump nitro to 3.0.260903-beta. With 3.0.1-alpha.1, nitro dev tree-shakes workflow's world registration and every start() fails with "world runtime was not initialized". - tanstack-start: re-resolve the lockfile. The pinned nitro-nightly build 404s the workflow flow route, so runs stay pending. - postgres, flight-booking-app: workflow-postgres-setup moved to bootstrap. - birthday-card-generator, kitchen-sink: replace model IDs the AI Gateway no longer serves. - hono: start script pointed at a file nitro never emits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5.0.1 publishes the 5.x @workflow/ai, fixes nuxt dev, and keeps step errors whose stack is read-only (postgres.js). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0d957da to
04b0b7d
Compare
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
Updates all 17 examples from
workflow4.3.1 to 5.0.1, including the v5 code changes validated in #51.workflow,@workflow/ai,@workflow/world-local,@workflow/world-postgres→5.0.1.@workflow/swc-pluginstays at5.0.0(no 5.0.1 was published).await getWorld()in instrumentation, custom-adapter on the v5 standalone bundle layout, ffmpeg-processing requires rollup >= 4.62.45.0.1 includes the SDK fixes found while running these examples: the 5.x
@workflow/aipublish (vercel/workflow#4548), errors with a read-onlystack(vercel/workflow#4549), and nuxt dev (vercel/workflow#4551).Fixes found by running every example on 5.0:
3.0.1-alpha.1→3.0.260903-beta. On alpha.1,nitro devtree-shakes the world registration and everystart()throws "world runtime was not initialized".nitro-nightlybuild 404s the flow route, so runs staypending.workflow-postgres-setupwas replaced bybootstrapin 5.0startscript pointed at a nonexistent fileVerification
Each example was started locally, a workflow triggered, and the run checked to reach its expected terminal state (
workflow inspect runs, or the Postgres table).On 5.0.1:
--frozen-lockfile) and buildOn 5.0.0, with the same example code (not re-run on 5.0.1):
withCreateHooknot run, needs a real OpenAI key)astro and sveltekit build with Vercel adapters and have no local prod server.
Known issues (not fixed here)
db:migratenever creates theembeddingstable (pre-existing;drizzle-kit pushworks around it).Supersedes #51.
🤖 Generated with Claude Code