Releases: dogmatiq/verity
Releases · dogmatiq/verity
Version 0.2.3
Changed
- Bumped Dogma to v0.14.0.
Version 0.2.2
Added
- Added support for
Disable()
method indogmatiq/dogma
v0.13.1.
Version 0.2.1
Changed
- Bump
dogmatiq/marshalkit
to v0.7.4, which introduces better handling of messages with conflicting names. - Add the new
stateless.DefaultCodec
to the default set of marshaling codecs as a special case fordogma.StatelessProcessRoot
values that does not depend on any other specific code, such as Protocol Buffers or JSON.
Version 0.2.0
- [BC] Bump
dogmatiq/dogma
to v0.13.0.
Version 0.1.8
Fixed
- Fixed
nil is not a message
error in event stream server.
Removed
- Removed
networkstream.NoopUnmarshaler
. This marshaler served as an optimization by skipping message unmarshaling when only the binary message data is needed. Unfortunately, this approach is incompatible withdogmatiq/marshalkit
as of v0.7.3.marshalkit
now explicitly requires unmarshaled messages to implement thedogma.Message
interface, because this interface is no longer equivalent toany
, as of Dogma v0.12.0.
Version 0.1.7
Added
- Enabled gRPC reflection service
Version 0.1.6
Changed
WithLogger()
now accepts either a*zap.Logger
or Dodecalogging.Logger
Version 0.1.5
This release updates Verity to adhere to Dogma v0.12.0 interfaces. Please note that Verity cannot support any projection delivery policies other than the default UnicastProjectionDeliveryPolicy
.
Version 0.1.4
- Bump
dogmatiq/marshalkit
to v0.7.3
Version 0.1.3
Fixed
- The
ExecuteCommand()
,RecordEvent()
orScheduleTimeout()
methods on the engine and handler scopes now panic if passed an invalid message.