Releases: Clarilab/clarimq
Releases · Clarilab/clarimq
v2.2.0
v2.0.0
V2 Release
BREAKING CHANGE:
Consumers now have to be started separately after their declaration
Why?: when used in services/applications, the main setup might has not yet fully finished initializing, but the consumers already consume messages from the broker, which can lead to panics, and even the app not starting at all.
Note: consumers can be switched back to the previous behaviour by using the
WithConsumerOptionConsumeAfterCreation() option while declaring the
consumer.
What's Changed
- feat: V2 - start consumers separately by @nicoandrewss in #18
Full Changelog: v1.5.0...v2.0.0
v1.5.0
What's Changed
- chore(deps): bump github.com/rabbitmq/amqp091-go from 1.9.0 to 1.10.0 by @dependabot in #14
- fix: panic on publisher close by @nicoandrewss in #16
- feat: add max retries exceeded handler by @nicoandrewss in #17
Full Changelog: v1.4.0...v1.5.0
v1.4.0
v1.3.0
What's Changed
- Add functionality to renew an existing connection by @nicoandrewss in #12
Full Changelog: v1.2.0...v1.3.0
v1.2.0
What's Changed
- feat: add getting connection name and accept logger interface by @nicoandrewss in #11
Full Changelog: v1.1.1...v1.2.0
v1.1.1
What's Changed
- chore(deps): bump github.com/rabbitmq/amqp091-go from 1.8.1 to 1.9.0 by @dependabot in #7
Full Changelog: v1.1.0...v1.1.1
v1.1.0
What's Changed
- Update go.yml by @MaxBreida in #8
- feat: add set connections options functions by @nicoandrewss in #9
v1.0.1
Merge pull request #6 from Clarilab/fix-go-version fix: go version in go.mod
v0.3.1
Merge pull request #6 from Clarilab/fix-go-version fix: go version in go.mod