Releases: NoeticTools/Git2SemVer.MSBuild
Releases · NoeticTools/Git2SemVer.MSBuild
v3.2.0
v3.1.0
v3.0.0
June 15, 2025
Git2SemVer.MSBuild 3.0.0 has breaking changes:
- The TeamCity version build time statistic was renamed from to
Git2SemVerRunTime_sec
togit2semver.runtime.seconds
. - Builds on Linux hosts (e.g: Ubuntu >= 22) may break with an error that
libdl.so
was not found.
For futher information see: Upgrading V2 to V3.
Added
- Warning if .net sdk 8.0 adding git SHA suffix to versions (#43).
- Further information in logs/report as to how the version is calculated (#42).
- Add warning and error IDs for MSBuild integration (#41).
Changed
- Breaking change - Improve build statistic naming (#44).
Fixed
v2.0.0
December 1, 2024
This release has breaking changes that will impact users that are either:
- Using the generated JSON
Git2SemVer.VersionInfo.g.json
file in custom code. - Using the Git API in custom C# script (csx) code.
Added
- C# scripting (csx):
Changed
- Breaking change to generated JSON file
Git2SemVer.VersionInfo.g.json
. These will only impact users using this file externally.- CommitId
Id
property renamed toSha
. CommitChangeTypeId
enumbNone
value (1) added. All higher numbers bumped.Rev
bumped to2
.- Others
- CommitId
- Breaking change
IGitTool
method signatures changed. Introduced Fluent API. - TeamCity automatic build label updating now adds build number metadata to release build label, e.g: 1.2.3+34567 (#33).
Fixed
- On a new repo without any release tags, conventional commit version bumps are ignored (#34).
v1.2.0
Changed
- Changed the build system label, as used by TeamCity, to include build number on release builds (#33).
- Moved Git2SemVer.Tool (dotnet tool) code to its own repository.
Known Issues
- Versioning fails build when TeamCity build configuration's VCS Root uses the option "Use tags as branches" is set (#32). A compile time exception is thrown.
1.1.0 Cross target project versioning
1.0.0 Initial release
First release.