V13.1.0

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

• @jwoodman510 made their first contribution in #399

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

V13.0.4

What's Changed

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

New Contributors

• @psampaio made their first contribution in #396

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

V13.0.3

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

V13.0.0

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

• @rizi made their first contribution in #392
• @ile-monad made their first contribution in #393

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

V12.1.0

.NET 8 support

V12.0.2

Fix for #340

v12.0.1

Just bug fixes: https://github.com/JasperFx/lamar/milestone/15?closed=1

Change to type scanning internals

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

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

https://github.com/JasperFx/lamar/issues?q=is%3Aclosed+milestone%3A4.3