●Change8

Migrating to Vercel Functions @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 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

  1. 1
    Migrate from `vercel-workers` to the new `vercel-queue` SDK for Python queue subscribers and workflows.
  2. 2
    Ensure projects using Celery or Dramatiq have the `vercel-celery` or `vercel-dramatiq` integration package injected or explicitly added as a dependency.
  3. 3
    For projects on `vercel` >= 0.8.0, ensure `[[tool.vercel.workflows]]` entrypoints are compatible with the new vercel-queue serving mechanism.
  4. 4
    If directly depending on `vercel-workers`, be aware that the legacy integration is maintained, but new projects should adopt `vercel-queue`.

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 and served, with automatic integration for Celery and Dramatiq projects.

Need More Details?

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

View Full Changelog