Celery Celery v5.3.6 release (Fix)

The Fix

Added changelog for v5.3.6 release, summarizing the changes and fixes made in this version.

Based on closed celery/celery issue #8642 · PR/commit linked

Jump to Verify Open PR/Commit

@@ -9,7 +9,37 @@ in the main branch & 5.3.x series, please see :ref:`whatsnew-5.3` for
 
 
-. _version-5.3.5:
+.. _version-5.3.6:
+

repro.py

.. _version-x.y.z:

x.y.z
=====

:release-date: YYYY-MM-DD HH:MM P.M/A.M TimeZone
:release-by: Release Manager Name

Changes list in RST format.

verify

Re-run the minimal reproduction on your broken version, then apply the fix and re-run.

fix.md

Option A — Apply the official fix\nAdded changelog for v5.3.6 release, summarizing the changes and fixes made in this version.\nWhen NOT to use: Do not use this fix if the changelog is not relevant to your application.\n\n

Why This Fix Works in Production

Trigger: - [x] Breaking Changes Validation
Mechanism: Added changelog for v5.3.6 release, summarizing the changes and fixes made in this version.

Why This Breaks in Prod

Production symptom (often without a traceback): - [x] Breaking Changes Validation

Proof / Evidence

GitHub issue: #8642
Fix PR: https://github.com/celery/celery/pull/8659
Reproduced locally: No (not executed)
Last verified: 2026-02-12
Confidence: 0.70
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.70

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“True, that already got positive feedback btw, and users can use the fix with the kombu release SQS fix without a new celery release”

@auvipy · 2023-11-19 · confirmation · source

“> True, that already got positive feedback btw, and users can use the fix with the kombu release SQS fix without a new celery release”

@Nusnus · 2023-11-19 · confirmation · source

“pending some further verification here https://github.com/celery/celery/pull/8632#discussion_r1397583914”

@auvipy · 2023-11-19 · source

“Reviewed #8633. Any ETA for completion on #8632? @auvipy”

@Nusnus · 2023-11-17 · source

Failure Signature (Search String)

- [x] Breaking Changes Validation
- [x] Compile Changelog

Copy-friendly signature

signature.txt

Failure Signature
-----------------
- [x] Breaking Changes Validation
- [x] Compile Changelog

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
- [x] Breaking Changes Validation
- [x] Compile Changelog

Minimal Reproduction

repro.py

.. _version-x.y.z:

x.y.z
=====

:release-date: YYYY-MM-DD HH:MM P.M/A.M TimeZone
:release-by: Release Manager Name

Changes list in RST format.

Fix Options (Details)

Option A — Apply the official fix

Added changelog for v5.3.6 release, summarizing the changes and fixes made in this version.

When NOT to use: Do not use this fix if the changelog is not relevant to your application.

Fix reference: https://github.com/celery/celery/pull/8659

Last verified: 2026-02-12. Validate in your environment.

When NOT to Use This Fix

Do not use this fix if the changelog is not relevant to your application.

Verify Fix

verify

Re-run the minimal reproduction on your broken version, then apply the fix and re-run.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Related Issues

No related fixes found.

Cluster: celery:auth Celery hub Celery best practices All hubs All clusters

Related clusters: Configuration error Data consistency Duplicates

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.