Repository navigation
pika 1.5.0 ships November 17, 2026: please try 1.5.0rc4 #375
Description
Note
Written by Claude Code under the direction of Luke Bakken (@lukebakken), a pika maintainer.
pika 1.5.0 ships on Tuesday, November 17, 2026, and from then a plain pip install pika gets it. pyoaev depends on pika, so this is advance notice and a request to try the release candidate first:
pip install --pre 'pika==1.5.0rc4'
What is most likely to affect pyoaev:
- Your pin blocks 1.5.0.
pika<1.5.0,>=1.4.4keeps pyoaev on 1.4.x, so nothing changes for your users until you widen it. Please try rc4 and widen the pin if it passes. BlockingConnectionnow 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.
The full list is in the 1.5.0 upgrade notes. Besides the deprecations, pika.compat is gone, pika.spec is now type-annotated (which can surface new type-checker errors), and an inbound message body above 64 MiB now closes the connection (configurable with max_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!
Activity
lukebakken commentedon Nov 4, 2026
Closing this so it doesn't sit in your issue list; it's a heads-up, not a bug report.
In the past, when I made a pika release, I only heard about problems after people upgraded. This time I looked for popular projects that use pika to let them know before 1.5.0 ships on November 17, since some changes may affect your code.
If you try rc4 and something breaks, please open an issue at https://github.com/pika/pika/issues. A note in pika/pika#1816 that it works is just as welcome. Apologies for the noise.