Skip to content

Releases: JasperFx/lamar

V13.1.0

16 Aug 01:05
Compare
Choose a tag to compare

What's Changed

  • Fix gh 398 hash collision mitigation by @jwoodman510 in #399
  • Adds support for Host.CreateApplicationBuilder() in Lamar.Microsoft.DependencyInjection
  • Some extra "special sauce" for integration with Wolverine 3.0

New Contributors

Full Changelog: V13.0.4...V13.1.0

V13.0.4

10 May 19:23
Compare
Choose a tag to compare

What's Changed

  • Check if service is keyed before accessing ImplementationType by @psampaio in #396

New Contributors

Full Changelog: V13.0.3...V13.0.4

V13.0.3

19 Feb 20:24
Compare
Choose a tag to compare

Little change to disallow Lamar from ever trying to fulfill Guid as a service dependency automatically

V13.0.0

14 Dec 16:45
Compare
Choose a tag to compare

What's Changed

  • Don't resolve collections for not registered types when IServiceProviderIsService is used - GH-391 by @rizi in #392
  • Fix typo in registry-dsl.md by @ile-monad in #393
  • All Lamar Nugets depend on >= 8.0.0 of the core .NET Nugets

New Contributors

Full Changelog: v12.1.0...V13.0.0

V12.1.0

15 Nov 16:22
Compare
Choose a tag to compare

.NET 8 support

V12.0.2

28 Sep 16:39
Compare
Choose a tag to compare

Fix for #340

v12.0.1

07 Sep 15:31
Compare
Choose a tag to compare

Change to type scanning internals

01 May 15:22
Compare
Choose a tag to compare

Lamar switched to using a synchronous type scanning model from JasperFx.Core vs the old asynchronous type scanning model from JasperFx.TypeDiscovery/BaselineTypeDiscovery/StructureMap. NO OTHER APIS OR BEHAVIOR CHANGED.

V11.0

05 Mar 19:25
Compare
Choose a tag to compare

This release strictly impacted the way that Wolverine (https://wolverine.netlify.app) uses Lamar for runtime code generation. This release will have zero impact on the mass majority of users as compared to Lamar 10 (honestly since > Lamar 5.0).

Bug fixes & new inverse registration options