Repository navigation
Update dependency celery to v5.6.3 - #96
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #96 +/- ##
==========================================
- Coverage 85.71% 83.92% -1.79%
==========================================
Files 5 5
Lines 112 112
==========================================
- Hits 96 94 -2
- Misses 16 18 +2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/celery-5.x-lockfile
branch
from
April 30, 2026 15:49
2667747 to
9149b94
Compare
renovate
Bot
force-pushed
the
renovate/celery-5.x-lockfile
branch
from
July 21, 2026 02:39
9149b94 to
c4c813b
Compare
renovate
Bot
force-pushed
the
renovate/celery-5.x-lockfile
branch
from
September 15, 2026 19:01
c4c813b to
5604bd8
Compare
renovate
Bot
force-pushed
the
renovate/celery-5.x-lockfile
branch
from
October 15, 2026 17:02
5604bd8 to
b1e27e0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
5.4.0→5.6.3Release Notes
celery/celery (celery)
v5.6.3Compare Source
What's Changed
TypeErrorduring exception handling by @ChickenBenny in #10178reconnect_on_errortoBaseResultConsumerby @ChickenBenny in #10189New Contributors
Full Changelog: celery/celery@v5.6.2...v5.6.3
v5.6.2Compare Source
=====
:release-date: 2026-01-04
:release-by: Tomer Nosrati
What's Changed
result_extendedvs periodic task metadata and showheaders["periodic_task_name"]example (#10030).. _version-5.6.0:
v5.6.1Compare Source
What's Changed
result_extendedvs periodic task metadata and showheaders["periodic_task_name"]example by @SpaceShaman in #10030New Contributors
Full Changelog: celery/celery@v5.6.0...v5.6.1
v5.6.0Compare Source
=====
:release-date: 2025-11-30
:release-by: Tomer Nosrati
Celery v5.6.0 is now available.
Key Highlights
.. _version-5.6.0rc2:
v5.5.3Compare Source
=====
:release-date: 2025-06-01
:release-by: Tomer Nosrati
What's Changed
setup_loggerfrom COMPAT_MODULES (#9668).. _version-5.5.1:
v5.5.2Compare Source
What's Changed
setup_loggerfrom COMPAT_MODULES by @rconradharris in #9668New Contributors
Full Changelog: celery/celery@v5.5.1...v5.5.2
v5.5.1Compare Source
=====
:release-date: 2025-04-08
:release-by: Tomer Nosrati
What's Changed
See :ref:
whatsnew-5.5for a complete overview or read the main highlights below.Redis Broker Stability Improvements
Long-standing disconnection issues with the Redis broker have been identified and
resolved in Kombu 5.5.0, which is included with this release. These improvements
significantly enhance stability when using Redis as a broker.
Additionally, the Redis backend now has better exception handling with the new
exception_safe_to_retryfeature, which improves resilience during temporaryRedis connection issues. See :ref:
conf-redis-result-backendfor completedocumentation.
Contributed by
@drienkop <https://github.com/drienkop>_ in#​9614 <https://github.com/celery/celery/pull/9614>_.pycurlreplaced withurllib3Replaced the :pypi:
pycurldependency with :pypi:urllib3.We're monitoring the performance impact of this change and welcome feedback from users
who notice any significant differences in their environments.
Contributed by
@spawn-guy <https://github.com/spawn-guy>_ in Kombu#​2134 <https://github.com/celery/kombu/pull/2134>_ and integrated in Celery via#​9526 <https://github.com/celery/celery/pull/9526>_.RabbitMQ Quorum Queues Support
Added support for RabbitMQ's new
Quorum Queues <https://www.rabbitmq.com/docs/quorum-queues>_feature, including compatibility with ETA tasks. This implementation has some limitations compared
to classic queues, so please refer to the documentation for details.
Native Delayed Delivery <https://docs.particular.net/transports/rabbitmq/delayed-delivery>_is automatically enabled when quorum queues are detected to implement the ETA mechanism.
See :ref:
using-quorum-queuesfor complete documentation.Configuration options:
broker_native_delayed_delivery_queue_type: Specifies the queue type fordelayed delivery (default:
quorum)task_default_queue_type: Sets the default queue type for tasks(default:
classic)worker_detect_quorum_queues: Controls automatic detection of quorumqueues (default:
True)Contributed in
#​9207 <https://github.com/celery/celery/pull/9207>,#​9121 <https://github.com/celery/celery/pull/9121>, and#​9599 <https://github.com/celery/celery/pull/9599>_.For details regarding the 404 errors, see
New Year's Security Incident <https://github.com/celery/celery/discussions/9525>_.Soft Shutdown Mechanism
Soft shutdown is a time limited warm shutdown, initiated just before the cold shutdown.
The worker will allow :setting:
worker_soft_shutdown_timeoutseconds for all currentlyexecuting tasks to finish before it terminates. If the time limit is reached, the worker
will initiate a cold shutdown and cancel all currently executing tasks.
This feature is particularly valuable when using brokers with visibility timeout
mechanisms, such as Redis or SQS. It allows the worker enough time to re-queue
tasks that were not completed before exiting, preventing task loss during worker
shutdown.
See :ref:
worker-stoppingfor complete documentation on worker shutdown types.Configuration options:
worker_soft_shutdown_timeout: Sets the duration in seconds for the softshutdown period (default:
0.0, disabled)worker_enable_soft_shutdown_on_idle: Controls whether soft shutdownshould be enabled even when the worker is idle (default:
False)Contributed by
@Nusnus <https://github.com/Nusnus>_ in#​9213 <https://github.com/celery/celery/pull/9213>,#​9231 <https://github.com/celery/celery/pull/9231>, and#​9238 <https://github.com/celery/celery/pull/9238>_.Pydantic Support
New native support for Pydantic models in tasks. This integration
allows you to leverage Pydantic's powerful data validation and serialization
capabilities directly in your Celery tasks.
Example usage:
.. code-block:: python
args/kwargs type hinted as Pydantic model will be converted
The returned model will be converted to a dict automatically
See :ref:
task-pydanticfor complete documentation.Configuration options:
pydantic=True: Enables Pydantic integration for the taskpydantic_strict=True/False: Controls whether strict validation is enabled(default:
False)pydantic_context={...}: Provides additional context for validationpydantic_dump_kwargs={...}: Customizes serialization behaviorContributed by
@mathiasertl <https://github.com/mathiasertl>_ in#​9023 <https://github.com/celery/celery/pull/9023>,#​9319 <https://github.com/celery/celery/pull/9319>, and#​9393 <https://github.com/celery/celery/pull/9393>_.Google Pub/Sub Transport
New support for Google Cloud Pub/Sub as a message transport, expanding
Celery's cloud integration options.
See :ref:
broker-gcpubsubfor complete documentation.For the Google Pub/Sub support you have to install additional dependencies:
.. code-block:: console
Then configure your Celery application to use the Google Pub/Sub transport:
.. code-block:: python
Contributed by
@haimjether <https://github.com/haimjether>_ in#​9351 <https://github.com/celery/celery/pull/9351>_.Python 3.13 Support
Official support for Python 3.13. All core dependencies have been
updated to ensure compatibility, including Kombu and py-amqp.
This release maintains compatibility with Python 3.8 through 3.13, as well as
PyPy 3.10+.
Contributed by
@Nusnus <https://github.com/Nusnus>_ in#​9309 <https://github.com/celery/celery/pull/9309>_ and#​9350 <https://github.com/celery/celery/pull/9350>_.REMAP_SIGTERM Support
The "REMAP_SIGTERM" feature, previously undocumented, has been tested, documented,
and is now officially supported. This feature allows you to remap the SIGTERM
signal to SIGQUIT, enabling you to initiate a soft or cold shutdown using TERM
instead of QUIT.
This is particularly useful in containerized environments where SIGTERM is the
standard signal for graceful termination.
See :ref:
Cold Shutdown documentation <worker-REMAP_SIGTERM>for more info.To enable this feature, set the environment variable:
.. code-block:: bash
Contributed by
@Nusnus <https://github.com/Nusnus>_ in#​9461 <https://github.com/celery/celery/pull/9461>_.Database Backend Improvements
New
create_tables_at_setupoption for the databasebackend. This option controls when database tables are created, allowing for
non-lazy table creation.
By default (
create_tables_at_setup=True), tables are created during backendinitialization. Setting this to
Falsedefers table creation until they areactually needed, which can be useful in certain deployment scenarios where you want
more control over database schema management.
See :ref:
conf-database-result-backendfor complete documentation.Configuration:
.. code-block:: python
Contributed by
@MarcBresson <https://github.com/MarcBresson>_ in#​9228 <https://github.com/celery/celery/pull/9228>_.What's Changed
See :ref:
whatsnew-5.5or read the main highlights below.Using Kombu 5.5.0rc3
The minimum required Kombu version has been bumped to 5.5.0.
Kombu is currently at 5.5.0rc3.
Complete Quorum Queues Support
A completely new ETA mechanism was developed to allow full support with RabbitMQ Quorum Queues.
After upgrading to this version, please share your feedback on the quorum queues support.
Relevant Issues:
#​9207 <https://github.com/celery/celery/discussions/9207>,#​6067 <https://github.com/celery/celery/discussions/6067>documentation <using-quorum-queues>.broker_native_delayed_delivery_queue_typeconfiguration option.New support for Google Pub/Sub transport
After upgrading to this version, please share your feedback on the Google Pub/Sub transport support.
Relevant Issues:
#​9351 <https://github.com/celery/celery/pull/9351>_Python 3.13 Improved Support
Additional dependencies have been migrated successfully to Python 3.13, including Kombu and py-amqp.
Soft Shutdown
The soft shutdown is a new mechanism in Celery that sits between the warm shutdown and the cold shutdown.
It sets a time limited "warm shutdown" period, during which the worker will continue to process tasks that are already running.
After the soft shutdown ends, the worker will initiate a graceful cold shutdown, stopping all tasks and exiting.
The soft shutdown is disabled by default, and can be enabled by setting the new configuration option :setting:
worker_soft_shutdown_timeout.If a worker is not running any task when the soft shutdown initiates, it will skip the warm shutdown period and proceed directly to the cold shutdown
unless the new configuration option :setting:
worker_enable_soft_shutdown_on_idleis set to True. This is useful for workersthat are idle, waiting on ETA tasks to be executed that still want to enable the soft shutdown anyways.
The soft shutdown can replace the cold shutdown when using a broker with a visibility timeout mechanism, like :ref:
Redis <broker-redis>or :ref:
SQS <broker-sqs>, to enable a more graceful cold shutdown procedure, allowing the worker enough time to re-queue tasks that were notcompleted (e.g.,
Restoring 1 unacknowledged message(s)) by resetting the visibility timeout of the unacknowledged messages just beforethe worker exits completely.
After upgrading to this version, please share your feedback on the new Soft Shutdown mechanism.
Relevant Issues:
#​9213 <https://github.com/celery/celery/pull/9213>,#​9231 <https://github.com/celery/celery/pull/9231>,#​9238 <https://github.com/celery/celery/pull/9238>_documentation <worker-stopping>for each shutdown type.worker_soft_shutdown_timeoutconfiguration option.worker_enable_soft_shutdown_on_idleconfiguration option.REMAP_SIGTERM
The
REMAP_SIGTERM"hidden feature" has been tested, :ref:documented <worker-REMAP_SIGTERM>and is now officially supported.This feature allows users to remap the SIGTERM signal to SIGQUIT, to initiate a soft or a cold shutdown using :sig:
TERMinstead of :sig:
QUIT.Pydantic Support
This release introduces support for Pydantic models in Celery tasks.
For more info, see the new pydantic example and PR
#​9023 <https://github.com/celery/celery/pull/9023>_ by [@mathiasertl]Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.