Releases: cbcrouse/Versioning.NET
Releases · cbcrouse/Versioning.NET
v0.8.1
0.8.1
What's Changed
- Refactored service composition to use
ServiceComposition.NETNuGet library - Removed unused AutoMapper dependency and related test infrastructure
Notes
- No functional changes to the console application
- This release contains internal structural improvements only
v0.8.0
🚀 Versioning.NET v0.8.0
This release focuses on a runtime and dependency upgrade, aligning the project with modern .NET and library versions. There are no intentional changes to end-user behavior, but one breaking requirement to be aware of.
⚠️ Breaking Change
.NET 10 Required
- Versioning.NET now requires .NET 10 (SDK and runtime) to build and run.
- All projects and CI workflows have been upgraded from earlier .NET versions.
- Consumers must upgrade their local and CI environments accordingly.
✨ What’s Changed
Dependency & Platform Upgrades
- Upgraded target framework across all projects to
net10.0 - Updated core dependencies to current versions, including:
- MediatR 12.5
- FluentValidation 12.x
- Semver 3.x
- AutoMapper, Serilog, Microsoft.Extensions.*, and related tooling
- Updated GitHub Actions workflows to use the .NET 10 SDK
Internal Refactoring (No Behavior Change)
- Adjusted MediatR request/handler and pipeline behavior usage to match 12.x semantics
- Fixed and aligned tests impacted by dependency behavior changes
- Removed brittle or invalid test assumptions exposed by upgrades
- Standardized dependency injection and validation execution paths
🧪 Testing & CI
- Test projects updated to reflect current MediatR and FluentValidation behavior
- Improved reliability of validation and pipeline execution in tests
- CI workflows simplified and clarified around SDK setup order
🧩 Compatibility Notes
- No intentional changes to command behavior or output
- CLI usage and flags remain the same
- Validation is now enforced consistently via MediatR pipelines under the upgraded stack
If you’re already on modern .NET tooling, this should be a smooth upgrade—just make sure .NET 10 is available in your environment.
v0.7.5
v0.7.4
v0.7.3
v0.7.2
v0.7.1
v0.7.0
v0.6.0
Major Changes
- The command
increment-version-with-githas been repurposed to allow support for manually supplying the version increment but still allowing for git integration. The previous behavior which utilized git commit messages to determine the version increment was migrated to the new commandincrement-version-with-git-hints. (#27)