Release Packages

[e0-gh-vercel-connect]

Package	Previous	Release
vercel-internal-core	0.2.0	0.2.1
vercel-oidc	0.9.0	0.10.0
vercel-connect	0.2.0	0.2.1
vercel-internal-telemetry	0.8.0	0.8.1
vercel-queue	0.9.0	0.9.1
vercel-sandbox	0.7.0	0.8.0
vercel-cache	0.7.5	0.7.6
vercel-workflow	0.11.0	0.11.1
vercel	0.11.4	0.11.5
vercel-apscheduler	0.3.2	0.3.3
vercel-celery	0.7.7	0.7.8
vercel-django-tasks	0.7.2	0.7.3
vercel-dramatiq	0.7.6	0.7.7

Changelogs

vercel-internal-core

0.2.1 - 2026-09-30

Internal

• Add shared environment-based coding-agent detection for SDK request attribution. (sandbox: Tag requests with coding agent #424)

vercel-oidc

0.10.0 - 2026-09-30

Features

• Support /var/run/secrets/vercel.com/token as an OIDC fallback with expiration-aware caching and automatic rereads for rotated tokens. (Support rotating mounted OIDC tokens #408)

vercel-connect

0.2.1 - 2026-09-30

• Update dependencies.

vercel-internal-telemetry

0.8.1 - 2026-09-30

• Update dependencies.

vercel-queue

0.9.1 - 2026-09-30

• Update dependencies.

vercel-sandbox

0.8.0 - 2026-09-30

Features

• Add open_interactive() for interactive PTY sessions. Terminal I/O is a standard stream on the session: an anyio.abc.ByteStream asynchronously and an io.RawIOBase synchronously, alongside resize() and wait() for the remote exit code. (sandbox: Add interactive PTY sessions #415)
• Tag Sandbox API requests with the coding agent driving the Python process, when detected, as an agent/<name> User-Agent phrase. This covers normal requests, streams, and uploads. (sandbox: Tag requests with coding agent #424)

Bug Fixes

• Allow Drive mounts to be combined with failover regions when creating sandboxes, while retaining primary-region validation. (sandbox: allow Drive mounts with failover regions #417)

vercel-cache

0.7.6 - 2026-09-30

• Update dependencies.

vercel-workflow

0.11.1 - 2026-09-30

Bug Fixes

• Fix missing workflow operations during replay being reported as runtime errors instead of nondeterminism errors. (workflow: fail missing operations as divergence #416)
• Fix workflow replay failures when a hook is disposed before its recorded registration is replayed. (workflow: fix replay failures for disposed hooks #419)
• Fail workflow replay when a hook's token differs from a token carried by its recorded events. (workflow: detect hook token divergence on replay #418)

vercel

0.11.5 - 2026-09-30

• Update dependencies.

vercel-apscheduler

0.3.3 - 2026-09-30

• Update dependencies.

vercel-celery

0.7.8 - 2026-09-30

• Update dependencies.

vercel-django-tasks

0.7.3 - 2026-09-30

• Update dependencies.

vercel-dramatiq

0.7.7 - 2026-09-30

• Update dependencies.

[e0-gh-vercel-connect]

The release publish dry run fails the same way in both runs (36727036441, 36727036777), and I can reproduce it locally every time. It isn't flaky and this PR didn't cause it, so I haven't rerun it or pushed anything here.

What fails: the installed-wheel tests for vercel-queue, and only 2 tests, both on the asyncio backend (trio passes):

• test_lease_renewal_start_async_cancellation_resets_and_stops[asyncio]
• test_lease_worker_processes_stop_while_extension_is_in_flight[asyncio]

Cause: the test harness ends up running with two separate copies of anyio.

• test_installed_wheel.sh rewrites import anyio and from anyio... import in the tests to point at the vendored copy. It misses import anyio.<submodule>.
• test_queue_lease.py line 17 has import anyio.from_thread. That line survives the rewrite and rebinds anyio to the real PyPI package, so the test builds its task group and cancel scope from real anyio while the library uses the vendored one.
• Until Fix anyio backend import in vendored deps. #423 this didn't matter, because vendored anyio still imported its asyncio backend from the top-level anyio, so both copies shared one backend. Fix anyio backend import in vendored deps. #423 fixed that import and shipped in vercel-internal-shared-vendored-deps 0.1.3 on 2026-09-28. This is the first vercel-queue release since then (the queue 0.9.0 dry run in Release Packages #391 passed). With separate backends, cancellation from the test's scope no longer reaches the library's scopes.

Evidence: I built the vercel-queue, vercel-internal-core, vercel-oidc and vercel-internal-telemetry bundles from this head and ran the harness locally: same 2 failures, 649 passed. Changing only line 17 of the rewritten test copy to import vercel.internal._vendor.anyio.from_thread makes test_queue_lease.py pass (109 passed). Pinning anyio, pytest, pytest-asyncio or trio to the lockfile versions did not help.

Next step: a small separate fix PR, then rebase or regenerate this release on top of it. Either fix works:

1. teach the harness rewrite to handle import <lib>.<submodule>, which also covers future tests, or
2. change the test to from anyio import from_thread.

I'd go with option 1. Happy to open it if you want.