v4.0.0

This is a feature and bugfix release, however due to the change of pushing annotated tags we've decided to make this a major bump, as it could have not-thought-of side effects for consumers.

What's Changed

• Create annotated git tags by @pingvinen in #117
• fix: don't break on csproj without a version set by @nover in #121

Full Changelog: v3.0.3...v4.0.0

v3.0.1

Breaking

• removed support for .net core 2.x, core 3.x and 5.x

New stuff

• added support for .net 8.x
• added support for VersionPrefix and VersionSuffix (thank you @jberude) (use flag --version-property-name to change default behavior of using Version)

New Contributors

• @jberude made their first contribution in #103

Full Changelog: v2.4.1...v3.0.1

v3.0.0

Please use v3.0.1

v2.4.1

This is a maintenance release with no breaking changes.

• Build target for dotnet7.0 to allow using the tool on machines with only this version installed
• Update vulnerable newtonsoft.json dependency to latest stable.

v2.3.0

This release addd dotnet 6 as publishing target. The tool should now be usable in dotnet 6 docker containers and other environments that only has dotnet 6 installed. See #93

v2.2.1

This is a bugfix release:

• fix return codes on error (see #89)

Thanks to @AWoelfel for reporting the issue.

v2.2.0

This is a feature and bugfix release

• add support for having a common version in a .targets file - check the readme (see #86)
• fix accidental breaking change that required .csproj files to have a PackageId. Snuck into the 2.1.x releases, sorry everyone! (see #87)

Thanks to @nikeee for providing the .targets support PR.

v2.1.3

this release fixes a bug relating to projects without a Title or PackageId

v2.1.2

This is a bugfix release:

• Fix problems with custom message and special chars in message / tag #74

v2.1.1

v2.1.1

This release note also covers 2.1.0 which failed to publish due to CI issues

• add bare output for dump and bump - only ouput version of target (see #72)
• add support for altering git tag and message (see #66)
• add tests specifically for dotnet 5.0 (see #64)
• tooling use official appveyor dotnet 5.0 image (see #67)