Repository navigation
pika 1.5.0 ships November 17, 2026: please try 1.5.0rc4 #1147
lukebakken
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Note
Written by Claude Code under the direction of @lukebakken, a pika maintainer.
pika 1.5.0 ships on Tuesday, November 17, 2026, and from then a plain
pip install pikagets it. testcontainers depends on pika, so this is advance notice and a request to try the release candidate first:What is most likely to affect testcontainers:
BlockingConnection, used by the RabbitMQ module'sreadiness_probe, now emits aDeprecationWarningfrom its constructor (it is removed in pika 2.0). It still works, but a test suite run with warnings as errors fails on it; the upgrade notes give a one-linefilterwarningsentry. The replacement is the new thread-safepika.Connection.IncompatibleProtocolErrorandAMQPConnectionError. We checked that against rc4 by restarting RabbitMQ 4.4.0 and connecting in a loop: while the broker boots, rc4 raises onlyIncompatibleProtocolError, as 1.4.4 does, so the probe keeps working unchanged.The full list is in the 1.5.0 upgrade notes. Besides the deprecations,
pika.compatis gone,pika.specis now type-annotated (which can surface new type-checker errors), and an inbound message body above 64 MiB now closes the connection (configurable withmax_inbound_message_body_size).If anything breaks, please open an issue at https://github.com/pika/pika/issues before November 17, 2026, even if it turns out to be intended. A short "our tests pass on rc4" reply here, or in pika/pika#1816, helps just as much. Thank you!
All reactions