Release Notes¶
v1.0.0b1¶
API Changes¶
fedora_messaging.message.Message.summary
is now a property rather than a method (#25).- The non-functional
--amqp-url
parameter has been removed from the CLI (#49).
Features¶
- Configuration parsing failures now produce point to the line and column of the parsing error (#21).
fedora_messaging.message.Message
now come with a set of standard accessors (#32).- Consumers can now specify whether a message should be re-queued when halting (#44).
- An example consumer that prints to standard output now ships with
fedora-messaging. It can be used by running
fedora-messaging consume --callback="fedora_messaging.example:printer"
(#40). fedora_messaging.message.Message
now have aseverity
associated with them (#48).
Bug Fixes¶
- Fix an issue where invalid or missing configuration files resulted in a traceback rather than a formatted error message from the CLI (#21).
- Client authentication with x509 now works with both the synchronous API and the Twisted API ( #29, #35).
fedora_messaging.api.publish()
no longer raises apika.exceptions.ChannelClosed
exception. Instead, it raises afedora_messaging.exceptions.ConnectionException
(#31).fedora_messaging.api.consume()
is now documented to raise aValueError
when the callback isn’t callable (#47).
Development Features¶
- The fedora-messaging code base is now compliant with the Black Python formatter and this is enforced with continuous integration.
- Test coverage is moving up and to the right.
Many thanks to the contributors of bug reports, pull requests, and pull request reviews for this release:
- Aurélien Bompard
- Clement Verna
- Ken Dreyer
- Jeremy Cline
- Miroslav Suchý
- Patrick Uiterwijk
- Sebastian Wojciechowski
v1.0.0a1¶
The initial alpha release for fedora-messaging v1.0.0. The API is not expected to change significantly between this release and the final v1.0.0 release, but it may do so if serious flaws are discovered in it.