ci: use matching Vercel deployment outputs

[NathanColosimo]

Summary

• Update every wait-for-deployment-action consumer to a commit that resolves deployment-url and deployment-id from the same environment-scoped GitHub deployment status.
• Prevent CI from pairing production and preview deployments when one commit is deployed to more than one environment.
• No workflow inputs, permissions, or secrets change.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4ffe845

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview	Jul 31, 2026 4:20am
example-nextjs-workflow-webpack	Ready	Preview	Jul 31, 2026 4:20am
example-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-astro-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-express-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-fastify-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-hono-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-nestjs-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-nitro-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-nuxt-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-sveltekit-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-tanstack-start-workflow	Ready	Preview	Jul 31, 2026 4:20am
workbench-vite-workflow	Ready	Preview	Jul 31, 2026 4:20am
workflow-docs	Ready	Preview, v0	Jul 31, 2026 4:20am
workflow-swc-playground	Ready	Preview	Jul 31, 2026 4:20am
workflow-tarballs	Ready	Preview	Jul 31, 2026 4:20am
workflow-web	Ready	Preview	Jul 31, 2026 4:20am

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

❌ Failed E2E Tests

📦 Local Production (1 failed)

nextjs-webpack-stable (1 failed):

• webhookWorkflow

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ 💻 Local Development	1486	0	208	1694
❌ 📦 Local Production	1620	1	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
✅ 📋 Other	768	0	156	924
Total	5649	1	818	6468

Details by Category

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

❌ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
❌ nextjs-webpack-stable	153	1	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	154	0	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	128	0	26
✅ e2e-local-dev-tanstack-start-	128	0	26
✅ e2e-local-postgres-nest-stable	128	0	26
✅ e2e-local-postgres-tanstack-start-	128	0	26
✅ e2e-local-prod-nest-stable	128	0	26
✅ e2e-local-prod-tanstack-start-	128	0	26

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

❌ The benchmark run for 4ffe845 failed. See the run logs for details.

No benchmark results were produced.

ℹ️ Metric definitions & methodology

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)}

_{All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.}

_{Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.}