Releases: rodri-oliveira-dev/Dapper-FluentMap
Release list
v3.0.3
Dapper-FluentMap 3.0.3
This release focuses on stabilizing the FluentMap 3.x package family, improving Dommel mapping behavior, modernizing package distribution, and making the release pipeline significantly more reliable.
Highlights
Simplified NuGet package identities
Three supporting packages now use FluentMap-focused NuGet package IDs:
Dapper.FluentMap.DependencyInjection→FluentMap.DependencyInjectionDapper.FluentMap.Analyzers→FluentMap.AnalyzersDapper.FluentMap.Generators→FluentMap.Generators
The core package identities remain unchanged:
Dapper.FluentMapDapper.FluentMap.Dommel
Only the NuGet package identities changed. Existing assembly names, namespaces, project identities, and public APIs are preserved.
For new installations:
dotnet add package Dapper.FluentMap --version 3.0.3
dotnet add package Dapper.FluentMap.Dommel --version 3.0.3
dotnet add package FluentMap.DependencyInjection --version 3.0.3
dotnet add package FluentMap.Analyzers --version 3.0.3
dotnet add package FluentMap.Generators --version 3.0.3Fixes
- Fixed Dommel property resolution so FluentMap configuration remains deferred until the result is enumerated.
- Preserved the expected behavior when mappings are registered after
ResolvePropertiesis called but before enumeration.
Maintainability
A broad internal refactoring reduced complexity across:
- core mapping validation;
- runtime materialization;
- analyzers;
- source generators;
- Dommel property/column resolution;
- release artifact validation.
These changes are internal and are intended to preserve existing public API and runtime behavior.
Packaging and tooling
- Modernized NuGet package metadata.
- Added and adopted the
.slnxsolution format while retaining the traditional.slnfor compatibility. - Updated Roslyn analyzer dependencies.
- Improved repository configuration and development tooling.
- Added stronger package metadata and release artifact validation.
Release reliability
The release infrastructure received substantial hardening in this version.
NuGet.org publication now treats package acceptance and package indexing as separate operations. All missing packages are submitted first, without blocking the package set while NuGet.org performs asynchronous validation and indexing.
After submission, the pipeline performs a bounded convergence phase and validates published primary package contents against the original release artifacts.
Release recovery is also resumable and idempotent, with safeguards for partially published releases.
Additional release safeguards include:
- NuGet Trusted Publishing through GitHub OIDC;
- independent symbol package publication;
- SHA-256 artifact verification;
- release manifests and dependency inventory;
- GitHub Packages publication;
- GitHub artifact attestations;
- package-content verification before skipping an already published version;
- protected recovery of incomplete releases without overwriting immutable packages.
Compatibility
No intentional public API breaking changes are introduced in 3.0.3.
Consumers of the Dependency Injection, Analyzer, or Generator packages should update their PackageReference to the new package IDs listed above.
Thanks to everyone using and contributing to Dapper-FluentMap. This release lays a stronger foundation for the FluentMap 3.x line, both for consumers and for future maintenance.
Full Changelog: v2.0.0...v3.0.3
v2.0.0
Dapper.FluentMap
- Update to Dapper 2.0.35
Dapper.FluentMap.Dommel
- Update to Dapper.FluentMap 2.0
- Update to Dommel 2.0
v1.8.1
Add conventions to the Dommel column name resolver
v1.8.0
v1.7.0
v1.6.0
- Update to .NET Core 2.0 SDK
- Update to .NET Standard library 1.6.1
Dapper.FluentMap.Dommel
- Release v1.5.0