feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends - #2789

Merged
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region
Jul 6, 2026
Merged

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends#2789
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jul 6, 2026

Copy link
Copy Markdown
Member

Based on main — mergeable ahead of #1981.

Problem

Token/proxy clients (CLI, dashboards, external scripts) send queue messages through api.vercel.com's /v1/workflow proxy, where the fixed resolveBaseUrl override replaces the queue SDK's own region → <region>.vercel-queue.com base-URL resolution. Every proxied send therefore lands on the region-less VQS host — while the direct in-function path already dials the regional host (iad1.vercel-queue.com today). Surfaced during the multi-region e2e work on #1981.

Change

The proxy now forwards sends to the region's VQS dataplane when x-vercel-queue-region is present. This PR sets that header on every proxy-mode send, carrying the region the QueueClient is constructed with. Direct (in-function) sends are unchanged.

Today that region is the static 'iad1', so the observable effect on main is proxied sends moving from vercel-queue.comiad1.vercel-queue.com (parity with the direct path). When #1981 lands, per-send region resolution (opts.region → run-ID tag → VERCEL_REGIONiad1) feeds the same construction, and the header automatically becomes region-aware — this PR is the transport mechanism, not the policy.

Tests

  • Proxy-mode construction carries the header matching the client's region (the suite's ./utils.js module mock pins usingProxy: false, so the test flips it via mockReturnValueOnce)
  • Direct-path construction doesn't send the header
  • world-vercel suite: 225/225 on main, build clean

CopilotAI review requested due to automatic review settings July 6, 2026 21:53
@TooTallNate
TooTallNate requested review from a team and ijjk as code ownersJuly 6, 2026 21:53
@changeset-bot

changeset-botBot commented Jul 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4938abb

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

This PR includes changesets to release 17 packages
NameType
@workflow/world-vercelPatch
@workflow/buildersPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/vitestPatch
workflowPatch
@workflow/world-testingPatch
@workflow/web-sharedPatch

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

vercelBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production144202301672
✅ 💻 Local Development160502191824
✅ 📦 Local Production160502191824
✅ 🐘 Local Postgres160502191824
✅ 🪟 Windows15200152
✅ 📋 Other88701771064
Total7296010648360

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro125027
✅ example125027
✅ express125027
✅ fastify125027
✅ hono125027
✅ nextjs-turbopack14903
✅ nextjs-webpack14903
✅ nitro125027
✅ nuxt125027
✅ sveltekit14408
✅ vite125027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15200
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable127025
✅ e2e-local-dev-tanstack-start-127025
✅ e2e-local-postgres-nest-stable127025
✅ e2e-local-postgres-tanstack-start-127025
✅ e2e-local-prod-nest-stable127025
✅ e2e-local-prod-tanstack-start-127025
✅ e2e-vercel-prod-tanstack-start125027

📋 View full workflow run

CopilotAI 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.

Pull request overview

Adds region-awareness to proxy-mode queue sends in @workflow/world-vercel by forwarding the per-send resolved region via an HTTP header so api.vercel.com/v1/workflow can route to the correct regional VQS dataplane.

Changes:

  • Attach x-vercel-queue-region to QueueClient request headers when usingProxy is enabled, using the same resolveTargetRegion() result already used for QueueClient’s region.
  • Add unit tests covering: proxy-mode header on explicit opts.region, proxy-mode header derived from tagged run ID, and ensuring the header is absent on the direct (non-proxy) path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/world-vercel/src/queue.tsAdds proxy-only x-vercel-queue-region request header injection based on the resolved target region.
packages/world-vercel/src/queue.test.tsAdds coverage verifying the header is sent in proxy mode (explicit + payload-derived) and not sent in direct mode.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Token/proxy clients (CLI, dashboards, external scripts) send queue
messages through api.vercel.com's /v1/workflow proxy, where the fixed
resolveBaseUrl override replaces the queue SDK's own
region -> <region>.vercel-queue.com base-URL resolution — so every
proxied send landed on the region-less VQS host, while the direct
in-function path already dials the regional host (iad1 today).
The proxy now routes sends to the region's VQS dataplane when the
x-vercel-queue-region header is present (vercel/api#79056, deployed).
Set it on every proxy-mode send from the region the QueueClient is
constructed with, giving proxy clients parity with the direct path.
Today that region is the static 'iad1'; when per-send region
resolution lands (#1981), the header automatically carries the
tag/option-derived region — this change is the transport mechanism,
not the policy.
Tests: proxy-mode construction carries the header matching the
client's region; the direct path doesn't.

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hardcoded to iad1 in this case is intentional right?

@github-actions

Copy link
Copy Markdown
Contributor

Backport to stable failed for 03862ed due to a workflow error (backport job run).

This is usually an infrastructure problem (e.g. the configured AI model could not be found, an AI Gateway error, or an opencode crash) rather than a merge conflict. Check the job logs linked above for details.

Once the underlying issue is fixed, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

03862edb651a37767df59c81898a8a4aadbb9d1c

Sign up for freeto 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.

4 participants

@TooTallNate@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends - #2789

Merged
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region
Jul 6, 2026
Merged

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends#2789
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jul 6, 2026

Copy link
Copy Markdown
Member

Based on main — mergeable ahead of #1981.

Problem

Token/proxy clients (CLI, dashboards, external scripts) send queue messages through api.vercel.com's /v1/workflow proxy, where the fixed resolveBaseUrl override replaces the queue SDK's own region → <region>.vercel-queue.com base-URL resolution. Every proxied send therefore lands on the region-less VQS host — while the direct in-function path already dials the regional host (iad1.vercel-queue.com today). Surfaced during the multi-region e2e work on #1981.

Change

The proxy now forwards sends to the region's VQS dataplane when x-vercel-queue-region is present. This PR sets that header on every proxy-mode send, carrying the region the QueueClient is constructed with. Direct (in-function) sends are unchanged.

Today that region is the static 'iad1', so the observable effect on main is proxied sends moving from vercel-queue.comiad1.vercel-queue.com (parity with the direct path). When #1981 lands, per-send region resolution (opts.region → run-ID tag → VERCEL_REGIONiad1) feeds the same construction, and the header automatically becomes region-aware — this PR is the transport mechanism, not the policy.

Tests

  • Proxy-mode construction carries the header matching the client's region (the suite's ./utils.js module mock pins usingProxy: false, so the test flips it via mockReturnValueOnce)
  • Direct-path construction doesn't send the header
  • world-vercel suite: 225/225 on main, build clean

CopilotAI review requested due to automatic review settings July 6, 2026 21:53
@TooTallNate
TooTallNate requested review from a team and ijjk as code ownersJuly 6, 2026 21:53
@changeset-bot

changeset-botBot commented Jul 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4938abb

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

This PR includes changesets to release 17 packages
NameType
@workflow/world-vercelPatch
@workflow/buildersPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/vitestPatch
workflowPatch
@workflow/world-testingPatch
@workflow/web-sharedPatch

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

vercelBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production144202301672
✅ 💻 Local Development160502191824
✅ 📦 Local Production160502191824
✅ 🐘 Local Postgres160502191824
✅ 🪟 Windows15200152
✅ 📋 Other88701771064
Total7296010648360

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro125027
✅ example125027
✅ express125027
✅ fastify125027
✅ hono125027
✅ nextjs-turbopack14903
✅ nextjs-webpack14903
✅ nitro125027
✅ nuxt125027
✅ sveltekit14408
✅ vite125027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15200
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable127025
✅ e2e-local-dev-tanstack-start-127025
✅ e2e-local-postgres-nest-stable127025
✅ e2e-local-postgres-tanstack-start-127025
✅ e2e-local-prod-nest-stable127025
✅ e2e-local-prod-tanstack-start-127025
✅ e2e-vercel-prod-tanstack-start125027

📋 View full workflow run

CopilotAI 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.

Pull request overview

Adds region-awareness to proxy-mode queue sends in @workflow/world-vercel by forwarding the per-send resolved region via an HTTP header so api.vercel.com/v1/workflow can route to the correct regional VQS dataplane.

Changes:

  • Attach x-vercel-queue-region to QueueClient request headers when usingProxy is enabled, using the same resolveTargetRegion() result already used for QueueClient’s region.
  • Add unit tests covering: proxy-mode header on explicit opts.region, proxy-mode header derived from tagged run ID, and ensuring the header is absent on the direct (non-proxy) path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/world-vercel/src/queue.tsAdds proxy-only x-vercel-queue-region request header injection based on the resolved target region.
packages/world-vercel/src/queue.test.tsAdds coverage verifying the header is sent in proxy mode (explicit + payload-derived) and not sent in direct mode.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Token/proxy clients (CLI, dashboards, external scripts) send queue
messages through api.vercel.com's /v1/workflow proxy, where the fixed
resolveBaseUrl override replaces the queue SDK's own
region -> <region>.vercel-queue.com base-URL resolution — so every
proxied send landed on the region-less VQS host, while the direct
in-function path already dials the regional host (iad1 today).
The proxy now routes sends to the region's VQS dataplane when the
x-vercel-queue-region header is present (vercel/api#79056, deployed).
Set it on every proxy-mode send from the region the QueueClient is
constructed with, giving proxy clients parity with the direct path.
Today that region is the static 'iad1'; when per-send region
resolution lands (#1981), the header automatically carries the
tag/option-derived region — this change is the transport mechanism,
not the policy.
Tests: proxy-mode construction carries the header matching the
client's region; the direct path doesn't.

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hardcoded to iad1 in this case is intentional right?

@github-actions

Copy link
Copy Markdown
Contributor

Backport to stable failed for 03862ed due to a workflow error (backport job run).

This is usually an infrastructure problem (e.g. the configured AI model could not be found, an AI Gateway error, or an opencode crash) rather than a merge conflict. Check the job logs linked above for details.

Once the underlying issue is fixed, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

03862edb651a37767df59c81898a8a4aadbb9d1c

Sign up for freeto 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.

4 participants

@TooTallNate@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends - #2789

Merged
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region
Jul 6, 2026
Merged

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends#2789
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jul 6, 2026

Copy link
Copy Markdown
Member

Based on main — mergeable ahead of #1981.

Problem

Token/proxy clients (CLI, dashboards, external scripts) send queue messages through api.vercel.com's /v1/workflow proxy, where the fixed resolveBaseUrl override replaces the queue SDK's own region → <region>.vercel-queue.com base-URL resolution. Every proxied send therefore lands on the region-less VQS host — while the direct in-function path already dials the regional host (iad1.vercel-queue.com today). Surfaced during the multi-region e2e work on #1981.

Change

The proxy now forwards sends to the region's VQS dataplane when x-vercel-queue-region is present. This PR sets that header on every proxy-mode send, carrying the region the QueueClient is constructed with. Direct (in-function) sends are unchanged.

Today that region is the static 'iad1', so the observable effect on main is proxied sends moving from vercel-queue.comiad1.vercel-queue.com (parity with the direct path). When #1981 lands, per-send region resolution (opts.region → run-ID tag → VERCEL_REGIONiad1) feeds the same construction, and the header automatically becomes region-aware — this PR is the transport mechanism, not the policy.

Tests

  • Proxy-mode construction carries the header matching the client's region (the suite's ./utils.js module mock pins usingProxy: false, so the test flips it via mockReturnValueOnce)
  • Direct-path construction doesn't send the header
  • world-vercel suite: 225/225 on main, build clean

CopilotAI review requested due to automatic review settings July 6, 2026 21:53
@TooTallNate
TooTallNate requested review from a team and ijjk as code ownersJuly 6, 2026 21:53
@changeset-bot

changeset-botBot commented Jul 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4938abb

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

This PR includes changesets to release 17 packages
NameType
@workflow/world-vercelPatch
@workflow/buildersPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/vitestPatch
workflowPatch
@workflow/world-testingPatch
@workflow/web-sharedPatch

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

vercelBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production144202301672
✅ 💻 Local Development160502191824
✅ 📦 Local Production160502191824
✅ 🐘 Local Postgres160502191824
✅ 🪟 Windows15200152
✅ 📋 Other88701771064
Total7296010648360

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro125027
✅ example125027
✅ express125027
✅ fastify125027
✅ hono125027
✅ nextjs-turbopack14903
✅ nextjs-webpack14903
✅ nitro125027
✅ nuxt125027
✅ sveltekit14408
✅ vite125027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15200
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable127025
✅ e2e-local-dev-tanstack-start-127025
✅ e2e-local-postgres-nest-stable127025
✅ e2e-local-postgres-tanstack-start-127025
✅ e2e-local-prod-nest-stable127025
✅ e2e-local-prod-tanstack-start-127025
✅ e2e-vercel-prod-tanstack-start125027

📋 View full workflow run

CopilotAI 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.

Pull request overview

Adds region-awareness to proxy-mode queue sends in @workflow/world-vercel by forwarding the per-send resolved region via an HTTP header so api.vercel.com/v1/workflow can route to the correct regional VQS dataplane.

Changes:

  • Attach x-vercel-queue-region to QueueClient request headers when usingProxy is enabled, using the same resolveTargetRegion() result already used for QueueClient’s region.
  • Add unit tests covering: proxy-mode header on explicit opts.region, proxy-mode header derived from tagged run ID, and ensuring the header is absent on the direct (non-proxy) path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/world-vercel/src/queue.tsAdds proxy-only x-vercel-queue-region request header injection based on the resolved target region.
packages/world-vercel/src/queue.test.tsAdds coverage verifying the header is sent in proxy mode (explicit + payload-derived) and not sent in direct mode.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Token/proxy clients (CLI, dashboards, external scripts) send queue
messages through api.vercel.com's /v1/workflow proxy, where the fixed
resolveBaseUrl override replaces the queue SDK's own
region -> <region>.vercel-queue.com base-URL resolution — so every
proxied send landed on the region-less VQS host, while the direct
in-function path already dials the regional host (iad1 today).
The proxy now routes sends to the region's VQS dataplane when the
x-vercel-queue-region header is present (vercel/api#79056, deployed).
Set it on every proxy-mode send from the region the QueueClient is
constructed with, giving proxy clients parity with the direct path.
Today that region is the static 'iad1'; when per-send region
resolution lands (#1981), the header automatically carries the
tag/option-derived region — this change is the transport mechanism,
not the policy.
Tests: proxy-mode construction carries the header matching the
client's region; the direct path doesn't.

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hardcoded to iad1 in this case is intentional right?

@github-actions

Copy link
Copy Markdown
Contributor

Backport to stable failed for 03862ed due to a workflow error (backport job run).

This is usually an infrastructure problem (e.g. the configured AI model could not be found, an AI Gateway error, or an opencode crash) rather than a merge conflict. Check the job logs linked above for details.

Once the underlying issue is fixed, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

03862edb651a37767df59c81898a8a4aadbb9d1c

Sign up for freeto 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.

4 participants

@TooTallNate@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends - #2789

Merged
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region
Jul 6, 2026
Merged

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends#2789
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jul 6, 2026

Copy link
Copy Markdown
Member

Based on main — mergeable ahead of #1981.

Problem

Token/proxy clients (CLI, dashboards, external scripts) send queue messages through api.vercel.com's /v1/workflow proxy, where the fixed resolveBaseUrl override replaces the queue SDK's own region → <region>.vercel-queue.com base-URL resolution. Every proxied send therefore lands on the region-less VQS host — while the direct in-function path already dials the regional host (iad1.vercel-queue.com today). Surfaced during the multi-region e2e work on #1981.

Change

The proxy now forwards sends to the region's VQS dataplane when x-vercel-queue-region is present. This PR sets that header on every proxy-mode send, carrying the region the QueueClient is constructed with. Direct (in-function) sends are unchanged.

Today that region is the static 'iad1', so the observable effect on main is proxied sends moving from vercel-queue.comiad1.vercel-queue.com (parity with the direct path). When #1981 lands, per-send region resolution (opts.region → run-ID tag → VERCEL_REGIONiad1) feeds the same construction, and the header automatically becomes region-aware — this PR is the transport mechanism, not the policy.

Tests

  • Proxy-mode construction carries the header matching the client's region (the suite's ./utils.js module mock pins usingProxy: false, so the test flips it via mockReturnValueOnce)
  • Direct-path construction doesn't send the header
  • world-vercel suite: 225/225 on main, build clean

CopilotAI review requested due to automatic review settings July 6, 2026 21:53
@TooTallNate
TooTallNate requested review from a team and ijjk as code ownersJuly 6, 2026 21:53
@changeset-bot

changeset-botBot commented Jul 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4938abb

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

This PR includes changesets to release 17 packages
NameType
@workflow/world-vercelPatch
@workflow/buildersPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/vitestPatch
workflowPatch
@workflow/world-testingPatch
@workflow/web-sharedPatch

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

vercelBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production144202301672
✅ 💻 Local Development160502191824
✅ 📦 Local Production160502191824
✅ 🐘 Local Postgres160502191824
✅ 🪟 Windows15200152
✅ 📋 Other88701771064
Total7296010648360

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro125027
✅ example125027
✅ express125027
✅ fastify125027
✅ hono125027
✅ nextjs-turbopack14903
✅ nextjs-webpack14903
✅ nitro125027
✅ nuxt125027
✅ sveltekit14408
✅ vite125027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15200
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable127025
✅ e2e-local-dev-tanstack-start-127025
✅ e2e-local-postgres-nest-stable127025
✅ e2e-local-postgres-tanstack-start-127025
✅ e2e-local-prod-nest-stable127025
✅ e2e-local-prod-tanstack-start-127025
✅ e2e-vercel-prod-tanstack-start125027

📋 View full workflow run

CopilotAI 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.

Pull request overview

Adds region-awareness to proxy-mode queue sends in @workflow/world-vercel by forwarding the per-send resolved region via an HTTP header so api.vercel.com/v1/workflow can route to the correct regional VQS dataplane.

Changes:

  • Attach x-vercel-queue-region to QueueClient request headers when usingProxy is enabled, using the same resolveTargetRegion() result already used for QueueClient’s region.
  • Add unit tests covering: proxy-mode header on explicit opts.region, proxy-mode header derived from tagged run ID, and ensuring the header is absent on the direct (non-proxy) path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/world-vercel/src/queue.tsAdds proxy-only x-vercel-queue-region request header injection based on the resolved target region.
packages/world-vercel/src/queue.test.tsAdds coverage verifying the header is sent in proxy mode (explicit + payload-derived) and not sent in direct mode.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Token/proxy clients (CLI, dashboards, external scripts) send queue
messages through api.vercel.com's /v1/workflow proxy, where the fixed
resolveBaseUrl override replaces the queue SDK's own
region -> <region>.vercel-queue.com base-URL resolution — so every
proxied send landed on the region-less VQS host, while the direct
in-function path already dials the regional host (iad1 today).
The proxy now routes sends to the region's VQS dataplane when the
x-vercel-queue-region header is present (vercel/api#79056, deployed).
Set it on every proxy-mode send from the region the QueueClient is
constructed with, giving proxy clients parity with the direct path.
Today that region is the static 'iad1'; when per-send region
resolution lands (#1981), the header automatically carries the
tag/option-derived region — this change is the transport mechanism,
not the policy.
Tests: proxy-mode construction carries the header matching the
client's region; the direct path doesn't.

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hardcoded to iad1 in this case is intentional right?

@github-actions

Copy link
Copy Markdown
Contributor

Backport to stable failed for 03862ed due to a workflow error (backport job run).

This is usually an infrastructure problem (e.g. the configured AI model could not be found, an AI Gateway error, or an opencode crash) rather than a merge conflict. Check the job logs linked above for details.

Once the underlying issue is fixed, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

03862edb651a37767df59c81898a8a4aadbb9d1c

Sign up for freeto 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.

4 participants

@TooTallNate@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends - #2789

Merged
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region
Jul 6, 2026
Merged

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends#2789
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jul 6, 2026

Copy link
Copy Markdown
Member

Based on main — mergeable ahead of #1981.

Problem

Token/proxy clients (CLI, dashboards, external scripts) send queue messages through api.vercel.com's /v1/workflow proxy, where the fixed resolveBaseUrl override replaces the queue SDK's own region → <region>.vercel-queue.com base-URL resolution. Every proxied send therefore lands on the region-less VQS host — while the direct in-function path already dials the regional host (iad1.vercel-queue.com today). Surfaced during the multi-region e2e work on #1981.

Change

The proxy now forwards sends to the region's VQS dataplane when x-vercel-queue-region is present. This PR sets that header on every proxy-mode send, carrying the region the QueueClient is constructed with. Direct (in-function) sends are unchanged.

Today that region is the static 'iad1', so the observable effect on main is proxied sends moving from vercel-queue.comiad1.vercel-queue.com (parity with the direct path). When #1981 lands, per-send region resolution (opts.region → run-ID tag → VERCEL_REGIONiad1) feeds the same construction, and the header automatically becomes region-aware — this PR is the transport mechanism, not the policy.

Tests

  • Proxy-mode construction carries the header matching the client's region (the suite's ./utils.js module mock pins usingProxy: false, so the test flips it via mockReturnValueOnce)
  • Direct-path construction doesn't send the header
  • world-vercel suite: 225/225 on main, build clean

CopilotAI review requested due to automatic review settings July 6, 2026 21:53
@TooTallNate
TooTallNate requested review from a team and ijjk as code ownersJuly 6, 2026 21:53
@changeset-bot

changeset-botBot commented Jul 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4938abb

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

This PR includes changesets to release 17 packages
NameType
@workflow/world-vercelPatch
@workflow/buildersPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/vitestPatch
workflowPatch
@workflow/world-testingPatch
@workflow/web-sharedPatch

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

vercelBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production144202301672
✅ 💻 Local Development160502191824
✅ 📦 Local Production160502191824
✅ 🐘 Local Postgres160502191824
✅ 🪟 Windows15200152
✅ 📋 Other88701771064
Total7296010648360

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro125027
✅ example125027
✅ express125027
✅ fastify125027
✅ hono125027
✅ nextjs-turbopack14903
✅ nextjs-webpack14903
✅ nitro125027
✅ nuxt125027
✅ sveltekit14408
✅ vite125027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15200
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable127025
✅ e2e-local-dev-tanstack-start-127025
✅ e2e-local-postgres-nest-stable127025
✅ e2e-local-postgres-tanstack-start-127025
✅ e2e-local-prod-nest-stable127025
✅ e2e-local-prod-tanstack-start-127025
✅ e2e-vercel-prod-tanstack-start125027

📋 View full workflow run

CopilotAI 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.

Pull request overview

Adds region-awareness to proxy-mode queue sends in @workflow/world-vercel by forwarding the per-send resolved region via an HTTP header so api.vercel.com/v1/workflow can route to the correct regional VQS dataplane.

Changes:

  • Attach x-vercel-queue-region to QueueClient request headers when usingProxy is enabled, using the same resolveTargetRegion() result already used for QueueClient’s region.
  • Add unit tests covering: proxy-mode header on explicit opts.region, proxy-mode header derived from tagged run ID, and ensuring the header is absent on the direct (non-proxy) path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/world-vercel/src/queue.tsAdds proxy-only x-vercel-queue-region request header injection based on the resolved target region.
packages/world-vercel/src/queue.test.tsAdds coverage verifying the header is sent in proxy mode (explicit + payload-derived) and not sent in direct mode.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Token/proxy clients (CLI, dashboards, external scripts) send queue
messages through api.vercel.com's /v1/workflow proxy, where the fixed
resolveBaseUrl override replaces the queue SDK's own
region -> <region>.vercel-queue.com base-URL resolution — so every
proxied send landed on the region-less VQS host, while the direct
in-function path already dials the regional host (iad1 today).
The proxy now routes sends to the region's VQS dataplane when the
x-vercel-queue-region header is present (vercel/api#79056, deployed).
Set it on every proxy-mode send from the region the QueueClient is
constructed with, giving proxy clients parity with the direct path.
Today that region is the static 'iad1'; when per-send region
resolution lands (#1981), the header automatically carries the
tag/option-derived region — this change is the transport mechanism,
not the policy.
Tests: proxy-mode construction carries the header matching the
client's region; the direct path doesn't.

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hardcoded to iad1 in this case is intentional right?

@github-actions

Copy link
Copy Markdown
Contributor

Backport to stable failed for 03862ed due to a workflow error (backport job run).

This is usually an infrastructure problem (e.g. the configured AI model could not be found, an AI Gateway error, or an opencode crash) rather than a merge conflict. Check the job logs linked above for details.

Once the underlying issue is fixed, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

03862edb651a37767df59c81898a8a4aadbb9d1c

Sign up for freeto 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.

4 participants

@TooTallNate@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends - #2789

Merged
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region
Jul 6, 2026
Merged

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends#2789
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jul 6, 2026

Copy link
Copy Markdown
Member

Based on main — mergeable ahead of #1981.

Problem

Token/proxy clients (CLI, dashboards, external scripts) send queue messages through api.vercel.com's /v1/workflow proxy, where the fixed resolveBaseUrl override replaces the queue SDK's own region → <region>.vercel-queue.com base-URL resolution. Every proxied send therefore lands on the region-less VQS host — while the direct in-function path already dials the regional host (iad1.vercel-queue.com today). Surfaced during the multi-region e2e work on #1981.

Change

The proxy now forwards sends to the region's VQS dataplane when x-vercel-queue-region is present. This PR sets that header on every proxy-mode send, carrying the region the QueueClient is constructed with. Direct (in-function) sends are unchanged.

Today that region is the static 'iad1', so the observable effect on main is proxied sends moving from vercel-queue.comiad1.vercel-queue.com (parity with the direct path). When #1981 lands, per-send region resolution (opts.region → run-ID tag → VERCEL_REGIONiad1) feeds the same construction, and the header automatically becomes region-aware — this PR is the transport mechanism, not the policy.

Tests

  • Proxy-mode construction carries the header matching the client's region (the suite's ./utils.js module mock pins usingProxy: false, so the test flips it via mockReturnValueOnce)
  • Direct-path construction doesn't send the header
  • world-vercel suite: 225/225 on main, build clean

CopilotAI review requested due to automatic review settings July 6, 2026 21:53
@TooTallNate
TooTallNate requested review from a team and ijjk as code ownersJuly 6, 2026 21:53
@changeset-bot

changeset-botBot commented Jul 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4938abb

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

This PR includes changesets to release 17 packages
NameType
@workflow/world-vercelPatch
@workflow/buildersPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/vitestPatch
workflowPatch
@workflow/world-testingPatch
@workflow/web-sharedPatch

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

vercelBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production144202301672
✅ 💻 Local Development160502191824
✅ 📦 Local Production160502191824
✅ 🐘 Local Postgres160502191824
✅ 🪟 Windows15200152
✅ 📋 Other88701771064
Total7296010648360

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro125027
✅ example125027
✅ express125027
✅ fastify125027
✅ hono125027
✅ nextjs-turbopack14903
✅ nextjs-webpack14903
✅ nitro125027
✅ nuxt125027
✅ sveltekit14408
✅ vite125027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15200
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable127025
✅ e2e-local-dev-tanstack-start-127025
✅ e2e-local-postgres-nest-stable127025
✅ e2e-local-postgres-tanstack-start-127025
✅ e2e-local-prod-nest-stable127025
✅ e2e-local-prod-tanstack-start-127025
✅ e2e-vercel-prod-tanstack-start125027

📋 View full workflow run

CopilotAI 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.

Pull request overview

Adds region-awareness to proxy-mode queue sends in @workflow/world-vercel by forwarding the per-send resolved region via an HTTP header so api.vercel.com/v1/workflow can route to the correct regional VQS dataplane.

Changes:

  • Attach x-vercel-queue-region to QueueClient request headers when usingProxy is enabled, using the same resolveTargetRegion() result already used for QueueClient’s region.
  • Add unit tests covering: proxy-mode header on explicit opts.region, proxy-mode header derived from tagged run ID, and ensuring the header is absent on the direct (non-proxy) path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/world-vercel/src/queue.tsAdds proxy-only x-vercel-queue-region request header injection based on the resolved target region.
packages/world-vercel/src/queue.test.tsAdds coverage verifying the header is sent in proxy mode (explicit + payload-derived) and not sent in direct mode.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Token/proxy clients (CLI, dashboards, external scripts) send queue
messages through api.vercel.com's /v1/workflow proxy, where the fixed
resolveBaseUrl override replaces the queue SDK's own
region -> <region>.vercel-queue.com base-URL resolution — so every
proxied send landed on the region-less VQS host, while the direct
in-function path already dials the regional host (iad1 today).
The proxy now routes sends to the region's VQS dataplane when the
x-vercel-queue-region header is present (vercel/api#79056, deployed).
Set it on every proxy-mode send from the region the QueueClient is
constructed with, giving proxy clients parity with the direct path.
Today that region is the static 'iad1'; when per-send region
resolution lands (#1981), the header automatically carries the
tag/option-derived region — this change is the transport mechanism,
not the policy.
Tests: proxy-mode construction carries the header matching the
client's region; the direct path doesn't.

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hardcoded to iad1 in this case is intentional right?

@github-actions

Copy link
Copy Markdown
Contributor

Backport to stable failed for 03862ed due to a workflow error (backport job run).

This is usually an infrastructure problem (e.g. the configured AI model could not be found, an AI Gateway error, or an opencode crash) rather than a merge conflict. Check the job logs linked above for details.

Once the underlying issue is fixed, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

03862edb651a37767df59c81898a8a4aadbb9d1c

Sign up for freeto 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.

4 participants

@TooTallNate@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends - #2789

Merged
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region
Jul 6, 2026
Merged

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends#2789
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jul 6, 2026

Copy link
Copy Markdown
Member

Based on main — mergeable ahead of #1981.

Problem

Token/proxy clients (CLI, dashboards, external scripts) send queue messages through api.vercel.com's /v1/workflow proxy, where the fixed resolveBaseUrl override replaces the queue SDK's own region → <region>.vercel-queue.com base-URL resolution. Every proxied send therefore lands on the region-less VQS host — while the direct in-function path already dials the regional host (iad1.vercel-queue.com today). Surfaced during the multi-region e2e work on #1981.

Change

The proxy now forwards sends to the region's VQS dataplane when x-vercel-queue-region is present. This PR sets that header on every proxy-mode send, carrying the region the QueueClient is constructed with. Direct (in-function) sends are unchanged.

Today that region is the static 'iad1', so the observable effect on main is proxied sends moving from vercel-queue.comiad1.vercel-queue.com (parity with the direct path). When #1981 lands, per-send region resolution (opts.region → run-ID tag → VERCEL_REGIONiad1) feeds the same construction, and the header automatically becomes region-aware — this PR is the transport mechanism, not the policy.

Tests

  • Proxy-mode construction carries the header matching the client's region (the suite's ./utils.js module mock pins usingProxy: false, so the test flips it via mockReturnValueOnce)
  • Direct-path construction doesn't send the header
  • world-vercel suite: 225/225 on main, build clean

CopilotAI review requested due to automatic review settings July 6, 2026 21:53
@TooTallNate
TooTallNate requested review from a team and ijjk as code ownersJuly 6, 2026 21:53
@changeset-bot

changeset-botBot commented Jul 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4938abb

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

This PR includes changesets to release 17 packages
NameType
@workflow/world-vercelPatch
@workflow/buildersPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/vitestPatch
workflowPatch
@workflow/world-testingPatch
@workflow/web-sharedPatch

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

vercelBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production144202301672
✅ 💻 Local Development160502191824
✅ 📦 Local Production160502191824
✅ 🐘 Local Postgres160502191824
✅ 🪟 Windows15200152
✅ 📋 Other88701771064
Total7296010648360

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro125027
✅ example125027
✅ express125027
✅ fastify125027
✅ hono125027
✅ nextjs-turbopack14903
✅ nextjs-webpack14903
✅ nitro125027
✅ nuxt125027
✅ sveltekit14408
✅ vite125027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15200
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable127025
✅ e2e-local-dev-tanstack-start-127025
✅ e2e-local-postgres-nest-stable127025
✅ e2e-local-postgres-tanstack-start-127025
✅ e2e-local-prod-nest-stable127025
✅ e2e-local-prod-tanstack-start-127025
✅ e2e-vercel-prod-tanstack-start125027

📋 View full workflow run

CopilotAI 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.

Pull request overview

Adds region-awareness to proxy-mode queue sends in @workflow/world-vercel by forwarding the per-send resolved region via an HTTP header so api.vercel.com/v1/workflow can route to the correct regional VQS dataplane.

Changes:

  • Attach x-vercel-queue-region to QueueClient request headers when usingProxy is enabled, using the same resolveTargetRegion() result already used for QueueClient’s region.
  • Add unit tests covering: proxy-mode header on explicit opts.region, proxy-mode header derived from tagged run ID, and ensuring the header is absent on the direct (non-proxy) path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/world-vercel/src/queue.tsAdds proxy-only x-vercel-queue-region request header injection based on the resolved target region.
packages/world-vercel/src/queue.test.tsAdds coverage verifying the header is sent in proxy mode (explicit + payload-derived) and not sent in direct mode.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Token/proxy clients (CLI, dashboards, external scripts) send queue
messages through api.vercel.com's /v1/workflow proxy, where the fixed
resolveBaseUrl override replaces the queue SDK's own
region -> <region>.vercel-queue.com base-URL resolution — so every
proxied send landed on the region-less VQS host, while the direct
in-function path already dials the regional host (iad1 today).
The proxy now routes sends to the region's VQS dataplane when the
x-vercel-queue-region header is present (vercel/api#79056, deployed).
Set it on every proxy-mode send from the region the QueueClient is
constructed with, giving proxy clients parity with the direct path.
Today that region is the static 'iad1'; when per-send region
resolution lands (#1981), the header automatically carries the
tag/option-derived region — this change is the transport mechanism,
not the policy.
Tests: proxy-mode construction carries the header matching the
client's region; the direct path doesn't.

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hardcoded to iad1 in this case is intentional right?

@github-actions

Copy link
Copy Markdown
Contributor

Backport to stable failed for 03862ed due to a workflow error (backport job run).

This is usually an infrastructure problem (e.g. the configured AI model could not be found, an AI Gateway error, or an opencode crash) rather than a merge conflict. Check the job logs linked above for details.

Once the underlying issue is fixed, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

03862edb651a37767df59c81898a8a4aadbb9d1c

Sign up for freeto 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.

4 participants

@TooTallNate@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends - #2789

Merged
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region
Jul 6, 2026
Merged

feat(world-vercel): send x-vercel-queue-region on proxy-mode queue sends#2789
TooTallNate merged 4 commits into
mainfrom
nate/world-vercel-proxy-queue-region

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jul 6, 2026

Copy link
Copy Markdown
Member

Based on main — mergeable ahead of #1981.

Problem

Token/proxy clients (CLI, dashboards, external scripts) send queue messages through api.vercel.com's /v1/workflow proxy, where the fixed resolveBaseUrl override replaces the queue SDK's own region → <region>.vercel-queue.com base-URL resolution. Every proxied send therefore lands on the region-less VQS host — while the direct in-function path already dials the regional host (iad1.vercel-queue.com today). Surfaced during the multi-region e2e work on #1981.

Change

The proxy now forwards sends to the region's VQS dataplane when x-vercel-queue-region is present. This PR sets that header on every proxy-mode send, carrying the region the QueueClient is constructed with. Direct (in-function) sends are unchanged.

Today that region is the static 'iad1', so the observable effect on main is proxied sends moving from vercel-queue.comiad1.vercel-queue.com (parity with the direct path). When #1981 lands, per-send region resolution (opts.region → run-ID tag → VERCEL_REGIONiad1) feeds the same construction, and the header automatically becomes region-aware — this PR is the transport mechanism, not the policy.

Tests

  • Proxy-mode construction carries the header matching the client's region (the suite's ./utils.js module mock pins usingProxy: false, so the test flips it via mockReturnValueOnce)
  • Direct-path construction doesn't send the header
  • world-vercel suite: 225/225 on main, build clean

CopilotAI review requested due to automatic review settings July 6, 2026 21:53
@TooTallNate
TooTallNate requested review from a team and ijjk as code ownersJuly 6, 2026 21:53
@changeset-bot

changeset-botBot commented Jul 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4938abb

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

This PR includes changesets to release 17 packages
NameType
@workflow/world-vercelPatch
@workflow/buildersPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/vitestPatch
workflowPatch
@workflow/world-testingPatch
@workflow/web-sharedPatch

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

vercelBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production144202301672
✅ 💻 Local Development160502191824
✅ 📦 Local Production160502191824
✅ 🐘 Local Postgres160502191824
✅ 🪟 Windows15200152
✅ 📋 Other88701771064
Total7296010648360

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro125027
✅ example125027
✅ express125027
✅ fastify125027
✅ hono125027
✅ nextjs-turbopack14903
✅ nextjs-webpack14903
✅ nitro125027
✅ nuxt125027
✅ sveltekit14408
✅ vite125027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable127025
✅ express-stable127025
✅ fastify-stable127025
✅ hono-stable127025
✅ nextjs-turbopack-canary133019
✅ nextjs-turbopack-stable15200
✅ nextjs-webpack-canary133019
✅ nextjs-webpack-stable15200
✅ nitro-stable127025
✅ nuxt-stable127025
✅ sveltekit-stable14606
✅ vite-stable127025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15200
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable127025
✅ e2e-local-dev-tanstack-start-127025
✅ e2e-local-postgres-nest-stable127025
✅ e2e-local-postgres-tanstack-start-127025
✅ e2e-local-prod-nest-stable127025
✅ e2e-local-prod-tanstack-start-127025
✅ e2e-vercel-prod-tanstack-start125027

📋 View full workflow run

CopilotAI 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.

Pull request overview

Adds region-awareness to proxy-mode queue sends in @workflow/world-vercel by forwarding the per-send resolved region via an HTTP header so api.vercel.com/v1/workflow can route to the correct regional VQS dataplane.

Changes:

  • Attach x-vercel-queue-region to QueueClient request headers when usingProxy is enabled, using the same resolveTargetRegion() result already used for QueueClient’s region.
  • Add unit tests covering: proxy-mode header on explicit opts.region, proxy-mode header derived from tagged run ID, and ensuring the header is absent on the direct (non-proxy) path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/world-vercel/src/queue.tsAdds proxy-only x-vercel-queue-region request header injection based on the resolved target region.
packages/world-vercel/src/queue.test.tsAdds coverage verifying the header is sent in proxy mode (explicit + payload-derived) and not sent in direct mode.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Token/proxy clients (CLI, dashboards, external scripts) send queue
messages through api.vercel.com's /v1/workflow proxy, where the fixed
resolveBaseUrl override replaces the queue SDK's own
region -> <region>.vercel-queue.com base-URL resolution — so every
proxied send landed on the region-less VQS host, while the direct
in-function path already dials the regional host (iad1 today).
The proxy now routes sends to the region's VQS dataplane when the
x-vercel-queue-region header is present (vercel/api#79056, deployed).
Set it on every proxy-mode send from the region the QueueClient is
constructed with, giving proxy clients parity with the direct path.
Today that region is the static 'iad1'; when per-send region
resolution lands (#1981), the header automatically carries the
tag/option-derived region — this change is the transport mechanism,
not the policy.
Tests: proxy-mode construction carries the header matching the
client's region; the direct path doesn't.

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hardcoded to iad1 in this case is intentional right?

@github-actions

Copy link
Copy Markdown
Contributor

Backport to stable failed for 03862ed due to a workflow error (backport job run).

This is usually an infrastructure problem (e.g. the configured AI model could not be found, an AI Gateway error, or an opencode crash) rather than a merge conflict. Check the job logs linked above for details.

Once the underlying issue is fixed, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

03862edb651a37767df59c81898a8a4aadbb9d1c

Sign up for freeto 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.

4 participants

@TooTallNate@VaguelySerious@karthikscale3