Halfway through a Django 6.0 upgrade on a client's compliance SaaS, I opened a branch called kill-celery . The plan was two hours of work: swap every @shared_task for the new built-in @task , drop the broker, delete the worker service, ship a smaller stack. I got as far as pasting a TASKS block into settings before I hit the sentence that closed the branch. Django's Tasks framework, in its own words, "does not provide a worker mechanism to run Tasks" — execution "must be handled by infrastructure outside Django, such as a separate process or service."
That is not a rough edge to be smoothed over in a point release. It is the declared scope of the feature, and it is the part most upgrade write-ups skip past on their way to the code sample.
What actually shipped
Django 6.0 arrived on December 3, 2025 with an API that standardises how background work is declared and enqueued , not how it is executed. You decorate a function, call .enqueue() , and get a TaskResult back:
# billing/tasks.py from django .…