Releases: wework/grabbit
Releases · wework/grabbit
v1.1.8
v1.1.7
v1.1.6
Point release containing additional functionality and bug fixes
Improvements
- Transactional outbox configuration #37
- Transactional outbox metrics #202
- The ability for producers to specify an idempotency key on the BusMessage. #106
Fixed Issues
- Messages get re-queued When GlobalRawMessageHandler returns an error #188
- AMQP channel shuts down when the GlobalRawMessageHandler returns an error #187
- Wrong started by saga identifier value was set when creating a new saga #194
- When a saga instance is not found in the saga store do not reject the message #196
- The target service was not resolved properly in SagaInvocation #195
- Saga store log entries do not contain the _service field #206
- Logger is lost at initialization #200
- Outbox stops trying sending a message after 50 attempts #203
- Handlers not resolved properly for messages returned from dead lettering #191
- migration entry with incorrect name #212
- Not all contextual data was logged when invoking handlers #217
v1.1.5
v1.1.4
v1.1.3
v1.1.2
v1.1.1
Point release rolling up fixes and improvements for the following issues
Improvements
Fixed Issues
v1.1.0
https://github.com/wework/grabbit/projects/1
Improvments
- Add the ability for handlers to track the number of execution attempts #95
- Expose the logger in the invocation #87
- Allow configuring max retries #84
- Report message handling metrics #103
- Persistent timeout manager #32
- Saga timeouts should be reported via a metric #113
- Improved documentation #38
- Support database migrations for grabbit mysql persistent store #42
- Cleanup logs #50
- Allow Sending Raw Messages #102
- Separate amqp connection for ingress and egress #46
Fixed Issues
- Shutting down txoutbox leaves dangling go routines #55
- Running two separate bus instances for the same service causes high CPU utilization #124
- A completing saga action may get executed twice #109
- Dead Letter Handler does not nack/ack after Processing #104
- Messages that originate from a saga and routed to the same service get rejected #64
- Closing rows when querying transactional outbox fails #91
- Saga configuration functions only run when saga created #74
- Transactions managed incorrectly between retries #81
v1.0.3
Point release rolling up fixes and improvements for the following issues