●Change8

Migrating to Vercel CLI @vercel/python@6.54.0

Version @vercel/python@6.54.0 introduces 1 breaking change. This guide details how to update your code.

Released: 7/29/2026

1
Breaking Changes
4
Migration Steps
8
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

tool.vercel.subscriberstool.vercel.workflowsvercel.queue.get_subscriptions()vercel.queue.asgi_app()vercel-celeryvercel-dramatiqvercel-workersconfig.hasWorkerServices

Breaking Changes

●Issue #1

The vercel-workers integration for Python queue subscribers and workflows has been replaced by the new vercel-queue SDK. Projects relying on the previous vercel-workers integration may need to adapt to the new SDK's entrypoint introspection, handler modules, and trigger mechanisms. Specifically, `[[tool.vercel.subscribers]]` and `[[tool.vercel.workflows]]` configurations will be handled differently. The CLI no longer injects `config.hasWorkerServices`; Python builder now makes queue-serving decisions from project metadata.

Migration Steps

  1. 1
    If using `[[tool.vercel.subscribers]]`, ensure your entrypoints are compatible with `vercel.queue.get_subscriptions()` and the generated `vercel.queue.asgi_app()` handler modules.
  2. 2
    If using `[[tool.vercel.workflows]]` with `vercel` < 0.8.0, be aware that older versions will keep the legacy vercel-workers serving.
  3. 3
    Projects depending directly on `vercel-workers` will continue to use the legacy integration. Consider migrating to the new `vercel-queue` SDK if possible.
  4. 4
    Update your project to use `vercel` >= 0.8.0 to leverage the new vercel-queue serving for workflows.

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

Need More Details?

View the full release notes and all changes for Vercel CLI @vercel/python@6.54.0.

View Full Changelog