@vercel/build-utils
15.5.0 · 18 Nov 2026Apache-2.07.9M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/build-utils From 13.36.0 to 13.36.1
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 6
- new
- 0
- fixes
Release by release
- New
[[tool.vercel.subscribers]]entrypoints are introspected at build time viavercel.queue.get_subscriptions()and served through generatedvercel.queue.asgi_app()handler modules, withqueue/v2betatriggers carrying the SDK-registered consumer groups and per-subscription tuning. - New
Celery and Dramatiq projects get the matching
vercel-celery/vercel-dramatiqintegration package injected automatically (bundled variant unlessvercel-queueis an explicit dependency), in builds and invercel dev. - New
[[tool.vercel.workflows]]entrypoints follow the SDK generation: projects onvercel>= 0.8.0 are served through vercel-queue like subscribers; older or undeterminable versions keep the legacy vercel-workers serving (worker env markers, injected pinnedvercel-workers). - New
Projects that depend on
vercel-workersdirectly keep the legacy integration wholesale: legacy subscriber schema, direct entrypoint serving, worker env markers. - New
vercel devserves queue sidecars throughvercel.queue.asgi_app()for new-SDK projects, and its queue broker delivers with the SDK-registered consumer groups introspected at sidecar startup (matching production trigger behavior); legacy projects keep the vercel-workers bootstrap. - New
The CLI no longer injects
config.hasWorkerServices; the Python builder makes all queue-serving decisions from project metadata.
- New
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.