Last 12 weeks · 1 commit
2 of 6 standards met
What Bumps the workflow deps in flight-booking-app and nextjs to the published v5.0.0-beta pre-release on npm. : , , : ( and have no published; and are their latest betas from the same release line.) v5 migration finding is now async in v5 (). The flight-booking-app called , which fails the type check and — more importantly — would silently no-op at runtime ( is on a Promise), so the world worker would never start. Fixed by awaiting: This is the only example using the optional async-world bootstrap, so it's the only one affected. Local testing nextjs: ✓; + started a run and both steps (create user, send welcome email) executed via the flow route ✓ flight-booking-app: ✓ (after the instrumentation fix); boots, homepage 200, "Initializing workflow World" logs ✓ (LLM chat path not exercised — no AI Gateway key configured locally) 🤖 Generated with Claude Code
Hey Vercel team! 👋 I ran a contribution analysis on workflow-examples using GitScope (an open-source git analysis tool) and wanted to share the insights. 📈 Key Stats 🔍 Interesting Patterns 8 contributors — healthy team collaboration High churn per commit (3,204 avg changes) — suggests large feature branches being merged 6-day streak — decent consistency The report includes interactive charts with contribution timelines, author breakdowns, and frequency patterns. 🔧 Try GitScope If this is useful, you can run your own analysis with: Free online tool: https://gitlog-viz.vercel.app Premium templates** (corporate/executive reports): https://gitscope-pro.vercel.app Would love any feedback on the tool! 🙏
Summary Bump all examples to the latest npm 4.x Workflow SDK (). Update compatible Workflow companion packages ( and to ; was already latest 4.x at ). Regenerate pnpm, npm, and Bun lockfiles across the examples. Apply audit fixes needed with current docs/build behavior: Nitro server examples use for Workflow 4.3.1 bundling, Astro uses the Vercel adapter, the Nitro Vite example resolves CSS via a Vite-compatible path, and the Vite starter now has a buildable React entry. Verification Confirmed npm latest 4.x versions for , , , and . Checked current Workflow SDK docs/API pages for the patterns used by these examples. Regenerated and frozen-installed pnpm/npm/Bun locks. Passed builds: , (), , , , , , , . Passed type checks: , , , , , , , . Passed lint. Note: a sequential Next.js production-build smoke test completed Workflow compilation and then stayed quiet in the Next/Turbopack optimization phase, so I stopped it rather than leave a hung process. The corresponding TypeScript checks passed for all Next examples.
Summary Replace , , and with workflow-docs preview tarballs from . Extend for all transitive packages so they resolve to the same preview deployment. Notes Tarball URLs include because the Vercel project has SSO protection on. This is the existing automation-bypass secret on the project. passes locally. Peer-dep warning about wanting beta-3 of workflow vs beta-4 found is benign — both versions come from the same v2-flow build. Test plan [ ] passes locally [ ] CI checks pass 🤖 Generated with Claude Code
Repository: vercel/workflow-examples. Description: Example projects and templates build using Workflow SDK Stars: 530, Forks: 81. Primary language: TypeScript. Languages: TypeScript (96.4%), CSS (3%), JavaScript (0.4%), HTML (0.2%), Svelte (0%). License: MIT. Homepage: https://workflowsdk.dev/ Open PRs: 7, open issues: 4. Last activity: 1mo ago. Community health: 50%. Top contributors: pranaygp, adriandlam, VaguelySerious, dancer, ethanniser, vercel[bot], TooTallNate, RhysSullivan, gt-codes, haydenbleasel and others.