[dependabot]

Bumps celery from 5.6.3 to 5.7.0.

Release notes

Sourced from celery's releases.

v5.7.0

Celery 5.7.0

We're pleased to announce Celery 5.7.0, a new stable release of Celery.

This release brings substantial improvements to task workflows, worker reliability, result handling, scheduling, and broker connectivity. It also includes new integrations, improved Python compatibility, performance optimizations, and a large number of bug fixes contributed by the community.

A significant part of this release focuses on making complex Canvas workflows more reliable and efficient, improving worker behavior during broker disconnections and shutdown, and making result-backend state handling more consistent.

Highlights

• More reliable Canvas workflows: Improved chains, groups, chords, nested workflows, callbacks, errbacks, and failure propagation. Several fixes also reduce unnecessary message growth in complex chains and chords.
• Improved worker reliability: Better connection recovery, graceful shutdown, prefork process management, autoscaling, and handling of worker-process loss.
• More predictable task results: Improved result-state consistency, retry handling, ignore_result behavior, and concurrent AsyncResult tracking.
• Timezone and scheduling improvements: More reliable ETA, countdown, expiration, crontab, solar schedules, and Celery Beat behavior across daylight-saving-time transitions.
• New Pydantic integration behavior: Tasks configured with pydantic=True can accept Pydantic model instances.
• New pymemcache result backend support: Adds support for using pymemcache as a result backend.
• Improved Redis result backend: New expiration settings for chord and failure results, improved Pub/Sub handling, and more reliable chord accounting.
• Better Python compatibility: Python 3.10 is now the minimum supported version, with compatibility work for newer Python versions, including Python 3.14.
• Improved worker operations: Cgroup-aware automatic concurrency detection and additional worker-management improvements.

What's New

Canvas, Chains, Groups, and Chords

Celery 5.7 includes extensive improvements to Canvas execution and composition, particularly for nested workflows and complex chains and chords.

• Fixed failure propagation through chained tasks into chord bodies.
• Improved chord failure handling when a chord header or a chained chord fails.
• Fixed chord error handling when the chord body is itself a chain.
• Improved handling of empty groups and chains, including empty groups inside chains and group headers.
• Chains are now constructed in a single pass instead of repeatedly folding signatures with the | operator.
• Reduced unnecessary message growth in chains of chords, chains of groups, implicit chords, and standalone chord bodies.
• Improved nested group handling and preservation of group IDs.
• Fixed duplicate nodes in GroupResult.as_tuple() after groups in chains.
• Improved GroupResult fan-out behavior in chains.
• Fixed eager execution behavior for chains containing Ignore or Reject.
• Avoided unnecessary result-backend access when eagerly applying groups inside chains.
• Improved task replacement with chains containing groups, including cases that previously could hang.
• Improved callback execution when a task is replaced by a chain, ensuring callbacks are not invoked repeatedly.
• Fixed eager-chain callback behavior so that chain links are dispatched once at the appropriate point.
• Improved propagation of task options, ETA, and countdown values to chord headers.
• Corrected the handling of link and link_error options on chords so they are applied to the chord body.
• Improved errback argument classification and handling of new-style errback calls.
• Preserved group errback mutability and improved stamped-header merging and revocation.
• Improved signature cloning and option isolation, preventing cloned signatures from sharing mutable keyword arguments with their originals.
• Fixed argument forwarding through nested chains during eager execution.
• Improved map and starmap option merging.

These changes make complex Canvas compositions more predictable and reduce unnecessary broker traffic and message growth.

... (truncated)

Changelog

Sourced from celery's changelog.

5.7.0

:release-date: 2026-11-05 :release-by: Asif Saif Uddin

Celery v5.7.0 Stable Release is now available for testing and deploy to production. Please help us test this version and report any issues.

What's Changed Since 5.7.0rc1

This section summarizes the changes made since the Celery 5.7.0rc1 pre-release.

Canvas, Chains, Groups, and Chords

• Run a replaced task's callbacks once when it is replaced with a chain (:ghpull:10927`).
• Fix chord link and link-error options so they are passed to the body only (:ghpull:10778`).
• Fix stamped header revocation (:ghpull:10884`).
• Count each chord header task only once in the Redis backend (:ghpull:10919`).
• Fix Redis chord claim cleanup ownership (:ghpull:10998`).
• Fail the chord when chord_unlock retry is refused by the broker (:ghpull:10959`).

Task Execution and Result Handling

• Fix retry argument conflicts when switching calling conventions (:ghpull:10895`).
• Pass values to backend hooks by position again (:ghpull:10918`).
• Don't mark a task REVOKED while another worker is running it (:ghpull:10922`).
• Keep the first SUCCESS in the database, MongoDB, and Cassandra backends (:ghpull:10920, :ghpull:10944, :ghpull:10945`).
• Don't record FAILURE when on_success raises after SUCCESS was stored (:ghpull:10759`).
• Don't fail a task whose SUCCESS was stored before the worker was lost (:ghpull:10752`).
• Fix a worker hang in WorkerLostError when result_backend_always_retry=True (:ghpull:10960`).
• Fix send_task() overriding ignore_result defaults (:ghpull:10953`).
• Preserve ignore_result overrides across task retries (:ghpull:10958`).
• Make Task.apply() respect the task.ignore_result default (:ghpull:11001`).
• Don't store RETRY for an ignored result when retrying after a lost worker (:ghpull:11009`).
• Track every AsyncResult waiting on a task ID (:ghpull:10956`).
• Allow ResultSet.add() after the set's results are ready (:ghpull:10930`).
• Use the documented retry defaults in the database backend (:ghpull:10921`).
• Fix Manager warning output during retries (:ghpull:10948`).
• Wait between retries when the broker refuses a callback publish (:ghpull:10975`).
• Merge signature options in map and starmap apply_async() (:ghpull:10787`).
• Stop gating task publishing signals on cached receiver lists (:ghpull:10791`).

Worker Operations

... (truncated)

Commits

• 6fcdbf9 Bump version: 5.7.0rc1 → 5.7.0 (#11025)
• 4a1d6f4 Make beat's pidbox stop test tolerate slow runners (#11024)
• 6a80d47 Added changelog and new features for celery v5.7.0 stable version (#11016)
• 6b67b23 Fix dead Akismet and vine zipball links in the docs (#11021)
• e82fa93 Chore(deps): Bump azure-identity from 1.26.0 to 1.27.0
• 2fe0ead Chore(deps): Bump google-cloud-storage from 3.15.0 to 3.17.1 (#11013)
• 89ce900 Fix#10997 - redis chord claim cleanup ownership (#10998)
• 5d83c46 Don't store RETRY for an ignored result when retrying after a lost worker (#1...
• 1f435e5 Use Cuba's 2025 fall-back in the midnight DST tests
• 98b7ba9 Update kombu version to 5.7.0 (#11007)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)