Skip to content

[astro] Stop Astro warning about the generated workflow manifest - #5183

Merged
VaguelySerious merged 1 commit into
mainfrom
peter/fix-astro-manifest-warning
Nov 2, 2026
Merged

VaguelySerious merged 1 commit into
mainfrom
peter/fix-astro-manifest-warning

Conversation

@VaguelySerious

Copy link
Copy Markdown
Member

On Astro 5, every build and dev route scan printed:

[WARN] Unsupported file type .../src/pages/.well-known/workflow/v1/manifest.json found. Prefix filename with an underscore (`_`) to ignore.

@workflow/astro writes the workflow manifest next to the generated routes in src/pages/.well-known/workflow/v1/. Astro 5 warns about any non-route file in the pages dir unless its name starts with _. Astro 6+ only warns for .tsx/.jsx/.vue/.svelte, which is why workbench/astro (Astro 7) never showed it. This is not a regression: the file has been there since the manifest was introduced, so 5.0.x warns on Astro 5 too.

Changes:

  • @workflow/astro: write the manifest as _manifest.json, the same _ convention the generated debug files and __step_registrations.js already use. Delete a leftover manifest.json from earlier builds. The WORKFLOW_PUBLIC_MANIFEST=1 route (manifest.json.js, served at /.well-known/workflow/v1/manifest.json) is unchanged.
  • @workflow/builders: createManifest takes an optional manifestFileName (default manifest.json).
  • @workflow/core: add /* @vite-ignore */ to the custom-world import(), which silences Vite's "dynamic import cannot be analyzed" warning for __step_registrations.js in Vite-based dev servers.

Consumers of the on-disk file: only the manifest.test.ts e2e check reads the Astro path (updated). The CLI and web UI manifest discovery never looked under src/pages, so nothing there changes.

Verification:

  • Astro 5.16 app with @astrojs/vercel: astro build printed the warning before and does not after. In astro dev, neither warning appears and a workflow run completes.
  • workbench/astro (WORKFLOW_PUBLIC_MANIFEST=1): build, manifest.test.ts, and a subset of e2e.test.ts against the prod server pass. The public manifest route still serves the JSON.

🤖 Generated with Claude Code

Write the Astro manifest as _manifest.json so Astro's router skips it, and
mark the custom-world dynamic import with @vite-ignore.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
example-nextjs-workflow-turbopack Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
example-nextjs-workflow-webpack Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
example-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-astro-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-express-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-fastify-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-hono-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-nestjs-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-nitro-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-nuxt-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-python-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-sveltekit-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-tanstack-start-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workbench-vite-workflow Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workflow-docs Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workflow-swc-playground Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workflow-tarballs Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC
workflow-web Ready Ready Preview, v0 Nov 2, 2026 6:57pm UTC

@changeset-bot

changeset-bot Bot commented Nov 2, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: baf2544

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

This PR includes changesets to release 17 packages
Name Type
@workflow/astro Patch
@workflow/builders Patch
@workflow/core Patch
workflow Patch
@workflow/cli Patch
@workflow/nest Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
@workflow/vite Patch
@workflow/vitest Patch
@workflow/web-shared Patch
@workflow/web Patch
@workflow/world-testing Patch
@workflow/nuxt Patch
@workflow/world-vercel Patch

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

@github-actions

github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit baf2544 · Mon, 02 Nov 2026 19:04:20 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric Scenario Best (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS step 1816 (+43%) 🔻 2071 🔴 (+30%) 🔻 2111 🔴 (+29%) 🔻 2204 🔴 (-16%) 💚 30
TTFS stream 1868 (+28%) 🔻 2036 🔴 (+30%) 🔻 2074 🔴 (+31%) 🔻 2097 🔴 (+28%) 🔻 30
TTFS hook + stream 573 (-68%) 💚 2348 🔴 (+24%) 🔻 2415 🔴 (+24%) 🔻 5606 🔴 (+169%) 🔻 30
Fan-out TTFS Promise.all(100 steps) 566 (-1.6%) 712 (-13%) 2375 (+143%) 🔻 2422 (+31%) 🔻 10
Fan-out TTLS Promise.all(100 steps) 1414 (-4.2%) 4167 (-2.3%) 6026 (+36%) 🔻 7824 (+21%) 🔻 10
STSO 1020 steps (inline) 89 (+2.3%) 111 (-5.1%) 128 (-7.2%) 193 (-49%) 💚 1019
WO 1020 steps 110966 (-7.2%) 110966 (-7.2%) 110966 (-7.2%) 110966 (-7.2%) 1
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 119106ms → this run 110388ms (Δ -8718ms, -7%)

 50-100 ms  ████████░░░░░┃            main 243  this 425  +182
100-150 ms  ██████████████████┃█████  main 717  this 562  -155
150-200 ms  ┃                         main  29  this  23    -6
200-250 ms  ┃                         main   9  this   3    -6
250-300 ms  ┃                         main   3  this   1    -2
300-350 ms  ┃                         main   7  this   3    -4
350-400 ms  ┃                         main   2  this   0    -2
400-450 ms  ┃                         main   3  this   1    -2
450-500 ms  ┃                         main   3  this   0    -3
500-550 ms  ┃                         main   2  this   0    -2
550-600 ms  ┃                         main   1  this   0    -1
600-650 ms  ┃                         main   0  this   1    +1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap, split inline (same warm process — pure framework overhead) vs queue-hop (fresh process — dispatch, reinit, replay). █ = main, ┃ = this run, ░ = fill.

Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.

Metrics — TTFS: time to first step body (in-deployment start() → first step body) · Fan-out TTFS: fan-out time to first step (in-deployment start() → first of the parallel step bodies to complete) · Fan-out TTLS: fan-out time to last step (in-deployment start() → last of the parallel step bodies to complete, i.e. when the Promise.all resolves) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored)

Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · Promise.all(100 steps): 100 trivial no-op steps started together in a single Promise.all; Fan-out TTFS is the first of them to complete and Fan-out TTLS the last, both from the in-deployment clientStart, so their gap is the spread the runtime adds across the fan-out

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600

All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = start() → first step body (includes dispatch + any cold start); Fan-out TTFS/TTLS = first/last step completion of one Promise.all from the same anchor (the gap is the runtime’s fan-out spread); STSO/WO between step bodies. Streaming delivery performance is measured in durabench.

Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor.

@github-actions

github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

❌ Some tests failed

❌ Failed E2E Tests

💻 Local Development (1 failed)

nextjs-webpack-stable-node (1 failed):

  • health check (CLI) - workflow health command reports healthy endpoints

⚠️ Flaky E2E Tests (passed on retry)

These tests failed at least once and passed on a retry. A recurring entry here is a real race worth investigating.

  • a duplicate start is refused naming the owner, and no run is created for it (nuxt · local-dev / local / node / stable)
  • abortTimeoutWorkflow: timeout cancels long-running step (python · vercel-prod / vercel / node / production)

🛠 Infra Events (absorbed by the harness)

Platform anomalies the e2e harness detected and worked around (e.g. a run the queue never picked up, replaced by a fresh run). Clustered timestamps indicate a backend blip; a steady drip indicates a platform issue worth escalating.

  • run-pickup-stall · runs app-generated source against a registered step (tanstack-start) · at 18:59:09Z · abandoned wrun_01M6ET1Y6XB6MT6EYX6M0NEBNB
  • cold-start-warmup · suite warmup (tanstack-start) · at 18:59:22Z · abandoned wrun_01M6ET1Y76PANC7457VB6VQQXT
  • run-pickup-stall · ChainableService.processWithThis - static step methods using this to reference the class (nextjs-webpack) · at 19:03:59Z · abandoned wrun_01M6ETARSNM780HGNWN79JYN9A

E2E Test Summary

Summary
Passed Failed Skipped Total
✅ ▲ Vercel Production 4008 0 1392 5400
❌ 💻 Local Development 5248 1 551 5800
✅ 📦 Local Production 5249 0 551 5800
✅ 🐘 Local Postgres 5249 0 551 5800
✅ 🪟 Windows 388 0 12 400
✅ 🌐 Cross-language Conformance 68 0 107 175
✅ dynamic-runs 0 0 0 0
✅ local-postgres-spec9 38 0 312 350
✅ vercel-http-transport 903 0 297 1200
✅ vercel-multi-region 27 0 0 27
✅ vercel-spec9 344 0 56 400
✅ vercel-ws-transport 611 0 189 800
Total 22133 1 4018 26152
Details by Category

✅ ▲ Vercel Production

App Passed Failed Skipped
✅ astro-node 146 0 54
✅ astro-quickjs 146 0 54
✅ example-node 146 0 54
✅ example-quickjs 146 0 54
✅ express-node 146 0 54
✅ express-quickjs 146 0 54
✅ fastify-node 146 0 54
✅ fastify-quickjs 146 0 54
✅ hono-node 146 0 54
✅ hono-quickjs 146 0 54
✅ nest-node 146 0 54
✅ nest-quickjs 146 0 54
✅ nextjs-turbopack-node 173 0 27
✅ nextjs-turbopack-quickjs 173 0 27
✅ nextjs-webpack-node 173 0 27
✅ nextjs-webpack-quickjs 173 0 27
✅ nitro-node 146 0 54
✅ nitro-quickjs 146 0 54
✅ nuxt-node 146 0 54
✅ nuxt-quickjs 146 0 54
✅ python-node 66 0 134
✅ sveltekit-node 165 0 35
✅ sveltekit-quickjs 165 0 35
✅ tanstack-start-node 146 0 54
✅ tanstack-start-quickjs 146 0 54
✅ vite-node 146 0 54
✅ vite-quickjs 146 0 54

❌ 💻 Local Development

App Passed Failed Skipped
✅ astro-stable-node 171 0 29
✅ astro-stable-quickjs 171 0 29
✅ express-stable-node 171 0 29
✅ express-stable-quickjs 171 0 29
✅ fastify-stable-node 171 0 29
✅ fastify-stable-quickjs 171 0 29
✅ hono-stable-node 171 0 29
✅ hono-stable-quickjs 171 0 29
✅ nest-stable-node 171 0 29
✅ nest-stable-quickjs 171 0 29
✅ nextjs-turbopack-canary-node 199 0 1
✅ nextjs-turbopack-canary-quickjs 199 0 1
✅ nextjs-turbopack-quickjs-snapshot 199 0 1
✅ nextjs-turbopack-stable-node 199 0 1
✅ nextjs-turbopack-stable-quickjs 199 0 1
✅ nextjs-webpack-canary-node 199 0 1
✅ nextjs-webpack-canary-quickjs 199 0 1
❌ nextjs-webpack-stable-node 198 1 1
✅ nextjs-webpack-stable-quickjs 199 0 1
✅ nitro-stable-node 171 0 29
✅ nitro-stable-quickjs 171 0 29
✅ nuxt-stable-node 171 0 29
✅ nuxt-stable-quickjs 171 0 29
✅ sveltekit-stable-node 190 0 10
✅ sveltekit-stable-quickjs 190 0 10
✅ tanstack-start-node 171 0 29
✅ tanstack-start-quickjs 171 0 29
✅ vite-stable-node 171 0 29
✅ vite-stable-quickjs 171 0 29

✅ 📦 Local Production

App Passed Failed Skipped
✅ astro-stable-node 171 0 29
✅ astro-stable-quickjs 171 0 29
✅ express-stable-node 171 0 29
✅ express-stable-quickjs 171 0 29
✅ fastify-stable-node 171 0 29
✅ fastify-stable-quickjs 171 0 29
✅ hono-stable-node 171 0 29
✅ hono-stable-quickjs 171 0 29
✅ nest-stable-node 171 0 29
✅ nest-stable-quickjs 171 0 29
✅ nextjs-turbopack-canary-node 199 0 1
✅ nextjs-turbopack-canary-quickjs 199 0 1
✅ nextjs-turbopack-quickjs-snapshot 199 0 1
✅ nextjs-turbopack-stable-node 199 0 1
✅ nextjs-turbopack-stable-quickjs 199 0 1
✅ nextjs-webpack-canary-node 199 0 1
✅ nextjs-webpack-canary-quickjs 199 0 1
✅ nextjs-webpack-stable-node 199 0 1
✅ nextjs-webpack-stable-quickjs 199 0 1
✅ nitro-stable-node 171 0 29
✅ nitro-stable-quickjs 171 0 29
✅ nuxt-stable-node 171 0 29
✅ nuxt-stable-quickjs 171 0 29
✅ sveltekit-stable-node 190 0 10
✅ sveltekit-stable-quickjs 190 0 10
✅ tanstack-start-node 171 0 29
✅ tanstack-start-quickjs 171 0 29
✅ vite-stable-node 171 0 29
✅ vite-stable-quickjs 171 0 29

✅ 🐘 Local Postgres

App Passed Failed Skipped
✅ astro-stable-node 171 0 29
✅ astro-stable-quickjs 171 0 29
✅ express-stable-node 171 0 29
✅ express-stable-quickjs 171 0 29
✅ fastify-stable-node 171 0 29
✅ fastify-stable-quickjs 171 0 29
✅ hono-stable-node 171 0 29
✅ hono-stable-quickjs 171 0 29
✅ nest-stable-node 171 0 29
✅ nest-stable-quickjs 171 0 29
✅ nextjs-turbopack-canary-node 199 0 1
✅ nextjs-turbopack-canary-quickjs 199 0 1
✅ nextjs-turbopack-quickjs-snapshot 199 0 1
✅ nextjs-turbopack-stable-node 199 0 1
✅ nextjs-turbopack-stable-quickjs 199 0 1
✅ nextjs-webpack-canary-node 199 0 1
✅ nextjs-webpack-canary-quickjs 199 0 1
✅ nextjs-webpack-stable-node 199 0 1
✅ nextjs-webpack-stable-quickjs 199 0 1
✅ nitro-stable-node 171 0 29
✅ nitro-stable-quickjs 171 0 29
✅ nuxt-stable-node 171 0 29
✅ nuxt-stable-quickjs 171 0 29
✅ sveltekit-stable-node 190 0 10
✅ sveltekit-stable-quickjs 190 0 10
✅ tanstack-start-node 171 0 29
✅ tanstack-start-quickjs 171 0 29
✅ vite-stable-node 171 0 29
✅ vite-stable-quickjs 171 0 29

✅ 🪟 Windows

App Passed Failed Skipped
✅ nextjs-turbopack-node 194 0 6
✅ nextjs-turbopack-quickjs 194 0 6

✅ 🌐 Cross-language Conformance

App Passed Failed Skipped
✅ python 68 0 107

✅ dynamic-runs

App Passed Failed Skipped
✅ astro-vercel 0 0 0
✅ example-vercel 0 0 0
✅ express-vercel 0 0 0
✅ fastify-vercel 0 0 0
✅ hono-vercel 0 0 0
✅ nest-vercel 0 0 0
✅ nextjs-turbopack-vercel 0 0 0
✅ nextjs-webpack-vercel 0 0 0
✅ nitro-vercel 0 0 0
✅ nuxt-vercel 0 0 0
✅ sveltekit-vercel 0 0 0
✅ tanstack-start-vercel 0 0 0
✅ vite-vercel 0 0 0

✅ local-postgres-spec9

App Passed Failed Skipped
✅ nextjs-turbopack-stable-node 19 0 156
✅ nextjs-turbopack-stable-quickjs 19 0 156

✅ vercel-http-transport

App Passed Failed Skipped
✅ example 146 0 54
✅ express 146 0 54
✅ hono 146 0 54
✅ nextjs-turbopack 173 0 27
✅ nitro 146 0 54
✅ vite 146 0 54

✅ vercel-multi-region

App Passed Failed Skipped
✅ nextjs-turbopack 27 0 0

✅ vercel-spec9

App Passed Failed Skipped
✅ nextjs-turbopack-node 172 0 28
✅ nextjs-turbopack-quickjs 172 0 28

✅ vercel-ws-transport

App Passed Failed Skipped
✅ example 146 0 54
✅ express 146 0 54
✅ nextjs-turbopack 173 0 27
✅ vite 146 0 54

📋 View full workflow run

@pranaygp pranaygp left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Renaming the on-disk Astro manifest to _manifest.json follows the same _ convention as the debug files and __step_registrations.js. The leftover-manifest.json cleanup only targets the old file, not the manifest.json.js public route. The only consumer of the on-disk path is the e2e manifest check, which this PR updates; the CLI and web discovery paths never looked under src/pages. createManifest's new manifestFileName defaults to the old name, so other builders don't change, and /* @vite-ignore */ is only a comment. base-builder-logging.test.ts passes locally. CI was still running when I approved, with no failures so far.

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Sim World

Simulated world deterministic testing for races. Traces

🟢 world-sim scenario book — 0 fail of 45 total
scenario outcome events virt replay violations
✅ smoke-no-steps completed 3 0ms ok 0
✅ smoke-one-step completed 5 0ms ok 0
✅ hook-at-step-started completed 9 0ms ok 0
✅ hook-at-step-completed completed 9 0ms ok 0
✅ hook-at-hook-created completed 9 0ms ok 0
✅ claim-hook-at-registration completed 9 0ms ok 0
✅ claim-hook-at-step-started completed 9 0ms ok 0
✅ deadline-hook-wins completed 6 1.0h ok 0
✅ deadline-expires completed 6 1.0h ok 0
✅ step-vs-timer-early-settlement completed 6 1.0h ok 0
✅ long-sleep completed 9 30.0d ok 0
✅ hook-never-arrives stalled 3 0ms skipped 0
✅ step-retries-twice completed 9 2.0s ok 0
✅ parallel-steps completed 7 0ms ok 0
✅ hook-on-execution-state completed 9 0ms ok 0
✅ peek-hook-before-branch completed 9 0ms ok 0
✅ peek-hook-after-branch completed 9 0ms ok 0
✅ peek-hook-at-registration completed 9 0ms ok 0
✅ race-hook-before-probe completed 9 0ms ok 0
✅ race-hook-after-probe completed 9 0ms ok 0
✅ race-duplicate-delivery completed 10 0ms ok 0
✅ attr-hook-before-step completed 9 0ms ok 0
✅ attr-hook-after-step completed 9 0ms ok 0
✅ attr-from-step-body completed 10 0ms ok 0
✅ fork-hook-after-timeout completed 11 1.0m ok 0
✅ fork-hook-before-timeout completed 11 1.0m ok 0
✅ count-hook-after-timeout completed 13 1.0m ok 0
✅ count-hook-before-timeout completed 15 1.0m ok 0
✅ stale-read-step-count-fork completed 15 1.0m ok 0
✅ stale-read-equal-step-counts completed 11 1.0m ok 0
✅ step-vs-step-fork completed 9 0ms ok 0
✅ step-vs-step-fork-fenced completed 9 1.0s ok 0
✅ fence-catches-benign-direction completed 9 1.0s ok 0
✅ run-ahead-fenced-overlap completed 10 1.0s ok 0
✅ in-flight-before-decision completed 15 1.0m ok 0
✅ in-flight-before-decision-counted completed 13 1.0m ok 0
✅ in-flight-after-decision completed 15 2.0m ok 0
✅ stale-read-step-count-fork-fenced completed 15 1.0m ok 0
✅ fork-hook-wins completed 10 1.0m ok 0
✅ fork-timeout-wins completed 10 1.0m ok 0
✅ unclaimed-payload-under-fork completed 14 1.0m ok 0
✅ claimed-payload-under-fork completed 14 1.0m ok 0
✅ writers-independent-step-bodies completed 9 0ms ok 0
✅ writers-scripted-tempo completed 9 0ms ok 0
✅ cancel-mid-step cancelled 6 0ms skipped 0

Full trace: world-sim.txt

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor
Framework Flow route Step reg. Framework output
hono 271.7 KiB (±0) 100.7 KiB (±0) 2.15 MiB (+12 B)
nextjs-turbopack 279.1 KiB (±0) 426 B (±0) 999.4 KiB (±0)
About these numbers

Sizes are gzip; parentheses show the change against main.
Flow route and Step reg. gate this job, on raw bytes rather than the gzip shown, at max(2%, 50.0 KiB). Framework output is informational.

baf2544 · run

@VaguelySerious
VaguelySerious marked this pull request as ready for review November 2, 2026 19:30
@VaguelySerious
VaguelySerious requested a review from a team as a code owner November 2, 2026 19:30
@VaguelySerious
VaguelySerious merged commit a54154e into main Nov 2, 2026
331 of 336 checks passed
@VaguelySerious
VaguelySerious deleted the peter/fix-astro-manifest-warning branch November 2, 2026 19:30
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

No backport to stable for a54154e (AI decision).

This change only silences build/dev warnings from Astro 5 and Vite. Nothing in the generated workflow output is broken, so it is log-noise cleanup rather than a stability fix. To get there it renames the on-disk Astro manifest to _manifest.json, which could break anything reading the old path on the maintenance line, and it adds a new manifestFileName option to createManifest. If someone wants the low-risk part on stable, the /* @vite-ignore */ comment in packages/core/src/runtime/world.ts could be split out and forced through via workflow_dispatch.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

a54154e6e13c821f4de57f678d4ef8776b7cf05c

@github-actions github-actions Bot mentioned this pull request Nov 2, 2026
pranaygp added a commit that referenced this pull request Nov 3, 2026
### Description

Docs follow-ups for user-facing changes merged on Nov 2 that shipped
without docs on these pages:

- **CLI and Web UI**, **Vercel World**: `--project` (ID or slug) and
`--team` take precedence over the `.vercel` link, and in a monorepo the
CLI uses the nearest `.vercel/project.json` (#5182).
- **`createWebhook`**: outside Vercel, `url` uses `PORT`, then the
detected server port (#5184).
- **Sequential and parallel cookbook**: says `Promise.race` behaves as
in plain JavaScript.

#5187 is being reverted, so it isn't documented here. #5100 is a bug fix
that makes `Promise.race` behave as users expect, so it needs no docs
beyond the cookbook wording. #5183, #5189, #5190 and #4909 don't change
anything users do.

### Docs Preview

- [CLI and Web UI:
`--project`](https://workflow-docs-git-workflow-docs-cleanup-tue-3-nov.vercel.sh/docs/configuration/cli-and-web-ui#--project)
- [Vercel World:
Observability](https://workflow-docs-git-workflow-docs-cleanup-tue-3-nov.vercel.sh/worlds/vercel#observability)
-
[createWebhook](https://workflow-docs-git-workflow-docs-cleanup-tue-3-nov.vercel.sh/docs/api-reference/workflow/create-webhook)
- [Sequential and parallel: How it
works](https://workflow-docs-git-workflow-docs-cleanup-tue-3-nov.vercel.sh/cookbook/common-patterns/sequential-and-parallel#how-it-works)

### PR Checklist - Required to merge

- [x] 🔒 DCO sign-off included on every commit

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Co-authored-by: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>

This branch was successfully deployed

1 active deployment
Preview – workflow-docs — baf2544f Deployed Nov 2, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants