- [Breaking] Drop Ruby
3.0
support according to the EOL schedule.
- [Fix] uninitialized constant
Karafka::Testing::Errors::ConsumerGroupNotFound
.
- [Enhancement] Provide
karafka.consumer_messages
to get (or alter) the messages that will go into created consumer. - [Fix]
#consumer_group_metadata_pointer
is not stubbed in the consumer client.
- [Enhancement] Memoize
consumer_for
so consumers can be set up for multiple topics andlet(:consumer)
is no longer a requirement. (dorner)
- [Fix] Fix: raw_key is not being assigned for rspec (CaioPenhalver)
- [Fix] Fix: raw_key is not being assigned for minitest
- [Fix] Fix: headers is not being assigned for minitest and rspec
- [Fix] Fix FrozenError when accessing key and headers in
Karafka::Messages::Metadata
(tldn0718)
- [Fix] Fix instance variable in minitest helper (tldn0718)
- [Breaking] Drop Ruby
2.7
support. - [Refactor] Extract common components for Minitest and RSpec.
- [Fix] Support again
require: false
on gem loading. - [Fix] Fix a case where multiplexed SG would fail with
TopicInManyConsumerGroupsError
- [Enhancement] Support
Minitest::Spec
.
- [Enhancement] Prevent usage of testing when Karafka is not loaded.
- [Enhancement] Prevent usage of testing when Karafka is not initialized.
- [Fix] Same CG multiplexing topic builder fails with
TopicInManyConsumerGroupsError
.
- [Maintenance] Release matching Karafka
2.3.0
release.
- [Feature] Provide support for Minitest (ValentinoRusconi-EH)
- [Enhancement] Support patterns in
#consumer_for
consumer builder.
- [Maintenance] Ensure that
2.2.0
works with consumers for patterns. - [Maintenance] Replace signing key with a new one (old expired).
- [Enhancement] Make
#used?
API always return true. - [Enhancement] Expand dummy client API with #seek.
- [Enhancement] User
prepend_before
instead ofprepend
for RSpec (ojab) - [Enhancement] Add support for client
#commit_offsets
and#commit_offsets!
stubs. - [Fix] Make sure that
#mark_as_consumed!
and#mark_as_consumed
return true.
- [Fix] Fix invalid consumer group assignment for consumers created for non-default consumer group when same topic is being used multiple times.
- [Enhancement] Align with Karafka
2.1.5
API.
- [Enhancement] Depend on WaterDrop
>=
2.6.0
directly and not via Karafka to make sure correct version is used. - [Fix] Use proper WaterDrop
>=
2.6.0
buffered client reference.
- [Enhancement] Support WaterDrop stubs with Mocha.
- [Maintenance] Align Karafka expectations to match
2.1.0
.
- Align metadata builder format with Karafka
2.0.40
.
- Align with changes in Karafka
2.0.39
- Replace direct
described_class
reference for consumer building withtopic.consumer
Karafka routing based one. This change will allow for usage ofkarafka.consumer_for
from any specs.
- Inject consumer strategy to the test consumer instance.
- Do not lock Ruby and rely on
karafka-core
viakarafka
. - Due to changes in the engine, lock to
2.0.20
.
- Release version with cert with valid access permissions (#114).
- Replace the
subject
reference with namedconsumer
reference. - Do not forward sent messages to
consumer
unless it's a Karafka consumer.
- Fix for: Test event production without defining a subject (#102)
- Align changes with Karafka
2.0.13
changes.
- Fix direct name reference
consumer
instead ofsubject
(#97).
- Provide multi-consumer group testing support (#92)
- Fail fast if requested topic is present in multiple consumer groups but consumer group is not specified.
- Allow for usage of
Karafka.producer
directly and make it buffered. - Rename
karafka.publish
tokarafka.produce
to align naming conventions [breaking change].
- Require non rc version of Karafka.
- No changes. Just non-rc release.
- Require Karafka
2.0.0.rc2
- Require Karafka
2.0.0.beta5
and fix non-existing coordinator reference
- Provide support for referencing producer from consumer
- Add
rubygems_mfa_required
- Change the API to be more comprehensive
- Update to work with Karafka 2.0
- Support for Ruby 3.1
- Drop support for ruby 2.6
If you are looking for the changelog of 1.4
, please go here.