v.2.0.0

What's Changed

• Verified CPM migration and dependency analysis by @TarasKovalenko in #3
• Build the pipelines on the .NET 10 SDK by @TarasKovalenko in #4

Full Changelog: v.1.1.1...v.2.0.0

CentralConfigGenerator v.1.1.1

What's Changed

• fixed: escape package names in version table

Full Changelog: https://github.com/TarasKovalenko/CentralConfigGenerator/commits/v.1.1.1

CentralConfigGenerator v1.1.0 - packages-enhanced

Excited to announce a major upgrade to CentralConfigGenerator!
I have just released the packages-enhanced command that takes package version management to the next level using NuGet. Versioning for intelligent semantic version analysis.

What's New:

• Enhanced version conflict resolution with semantic versioning support
• Visual conflict analysis with detailed warnings and recommendations
• Security vulnerability detection for package versions
• Interactive conflict resolution mode
• Support for version ranges and pre-release detection

Try it now:
central-config packages-enhanced -v

The new analyzer properly handles:

• Pre-release versions (1.0.0-beta.1)
• Version ranges ([1.0.0,2.0.0))
• Floating versions (1.0.*)
• Complex semantic versioning scenarios

No more guessing which version to use! The tool now provides intelligent recommendations based on semantic versioning rules, helping teams maintain consistent and secure package versions across large .NET solutions.

Perfect for teams managing multiple projects with shared dependencies. Save hours of manual version reconciliation and reduce security risks with automated compatibility checking.