Skip to content

Releases: Cratis/Chronicle

Release v15.3.2

28 Feb 00:25
a71a00d

Choose a tag to compare

Summary

This update addresses a packaging issue related to the Cratis.Chronicle.Infrastructure.dll.

Fixed

  • Include Cratis.Chronicle.Infrastructure.dll in the ref folder to prevent compilation errors when consumers reference the assembly. This change resolves the CS0012 error encountered during compilation without altering runtime behavior.

Release v15.3.1

24 Feb 18:56
2dc919d

Choose a tag to compare

Fixed

  • Getting rid of the DotNET.InProcess client type, since it is unsupported in the form it had. Doing this to fix type problems when using XUnit.Integration client.

Release v15.3.0

24 Feb 14:29
9b6317f

Choose a tag to compare

Added

  • Added convenience extension method for converting to an ISubject<TReadModel> from an IObservable<ReadModelChangeset<TReadModel>> returned from the Watch() method on IReadModels.

Fixed

  • Renaming internal IChronicleBuilder to IChronicleCoreBuilder due to C# compiler actually binding to the wrong one for some reason when using the Cratis.Chronicle.XUnit.Integration and Cratis.Chronicle.AspNetCore packages in same project.

Release v15.2.22

24 Feb 10:17
27ba8a8

Choose a tag to compare

Fixed

  • Fixing Client projects (Api, Testing) to have private project reference to internal project called Infrastructure, resulting in the assemblies being private and not relying on a public package.

Release v15.2.21

23 Feb 21:14
5cb6cce

Choose a tag to compare

Summary

Adds missing IReadModels service as scoped service

Fixed

  • Add IReadModelsservice as scoped service

Release v15.2.20

23 Feb 17:44

Choose a tag to compare

No release notes

Release v15.2.19

23 Feb 06:33
74a5352

Choose a tag to compare

Fixed

  • Making Rename-method on IReactorDefinitionsStorage transactional

Release v15.2.18

22 Feb 17:15
00476e7

Choose a tag to compare

Summary

Improved internal handling of client artifact lifecycle and activation. It noe behaves more like one would expect them to behave as if they were registered as scoped services in the service provider. They will also be disposed of properly if they implement a disposable interface.

Release v15.2.17

20 Feb 12:37

Choose a tag to compare

No release notes

Release v15.2.16

20 Feb 06:51

Choose a tag to compare

No release notes