@vercel/python-runtime@0.17.0
Breaking Changes📦 vercel-functionsView on GitHub →
⚠ 1 breaking✨ 6 features🔧 8 symbols
Summary
Replaced the vercel-workers integration with the new vercel-queue SDK for Python queue subscribers and workflows. This change impacts how entrypoints are introspected, served, and how `vercel dev` handles queue sidecars.
⚠️ Breaking Changes
- The vercel-workers integration for Python queue subscribers and workflows has been replaced by the new vercel-queue SDK. Projects relying on the old vercel-workers integration may need to migrate to the new SDK. The CLI no longer injects `config.hasWorkerServices`; the Python builder now makes all queue-serving decisions from project metadata.
Migration Steps
- Migrate from `vercel-workers` to the new `vercel-queue` SDK for Python queue subscribers and workflows.
- Ensure projects on `vercel` >= 0.8.0 are configured to use `vercel-queue` for workflow entrypoints.
- If your project depends directly on `vercel-workers`, you will keep the legacy integration. Consider migrating to the new SDK for future updates and features.
✨ New Features
- Introduced a new vercel-queue SDK for Python queue subscribers and workflows, replacing the vercel-workers integration.
- Entrypoints for `[[tool.vercel.subscribers]]` are now introspected at build time via `vercel.queue.get_subscriptions()` and served through generated `vercel.queue.asgi_app()` handler modules.
- Celery and Dramatiq projects automatically receive the `vercel-celery`/`vercel-dramatiq` integration package.
- Entrypoints for `[[tool.vercel.workflows]]` now follow the SDK generation, served through vercel-queue for projects on `vercel` >= 0.8.0.
- `vercel dev` now serves queue sidecars through `vercel.queue.asgi_app()` for new-SDK projects.
- The queue broker in `vercel dev` now delivers with SDK-registered consumer groups introspected at sidecar startup.