Bump gitversion.tool from 5.12.0 to 6.1.0 in /build

[dependabot]

Bumps gitversion.tool from 5.12.0 to 6.1.0.

Release notes

Sourced from gitversion.tool's releases.

6.1.0

As part of this release we had 62 commits which resulted in 9 issues being closed.

Dependencies

• !4302 (deps): Bump Cake.Frosting from 4.2.0 to 5.0.0 in /build

Documentation

• [#4299](GitTools/GitVersion#4299) Add new schemas for version 6.1.*
• !4308 Update the commit-message behavior docs
• !4317 fix: Typo in continuous-deployment.md

Features

• !4306 Add net9.0 target

Improvements

• !4279 Sunset .net 6.0
• !4316 cleanup code targeting < net8.0
• !4340 Improve IFileSystem usage in the app (part 1)

SHA256 Hashes of the release artifacts

• bb7187dee5aeb00a43fc2542ff9f7caee78329867202f0317da27efd5c52ab7b - gitversion-linux-arm64-6.1.0.tar.gz
• 0ca8bf5280e139f0e9eeffe9083d5dbbf3fc19759719d6af48f79b3fad3d778e - gitversion-linux-musl-arm64-6.1.0.tar.gz
• 2d3f8a05be8ece49185bcab5d8c0f05c6feb8e78adcc4424513718f2fc9e62b7 - gitversion-linux-musl-x64-6.1.0.tar.gz
• 800c0706108e20f768247c9a241d21476a9690cdafbbf4468c60af608c755644 - gitversion-linux-x64-6.1.0.tar.gz
• 235ef5588a888aeae3fd6ccfb6e84a2e0da6482b1d121b4c8ec0f156fc229ab8 - gitversion-osx-arm64-6.1.0.tar.gz
• a679e1a9c9aeb601124a776623e36e1cf3e2214e379e57904ce8ad7e742f3879 - gitversion-osx-x64-6.1.0.tar.gz
• 41362cf1edd72df13633612ab04a7f0a184b941b853f04d780d3a1b59e1a45d1 - gitversion-win-arm64-6.1.0.zip
• f78cdb446c77d9ad0ed84c26a73c55e89606e5b08e32f17b2ea05c4109901811 - gitversion-win-x64-6.1.0.zip

6.0.5

This is the last version supporting .net 6.0 as it's now End Of Support

As part of this release we had 12 commits which resulted in 5 issues being closed.

Documentation

• !4229 Update msbuild.md: Visual Studio is no longer supported
• [#4244](GitTools/GitVersion#4244) [ISSUE]: dotnet tool install docs should not use an explicit --version arg
• !4288 Mention new config parameter semantic-version-format

SHA256 Hashes of the release artifacts

• 0b4186c884bc4859a44f633141d2492838ad631e49b18aca2e5422d8b5f1fecf - gitversion-linux-arm64-6.0.5.tar.gz
• cf74d02985e3cfa6deee2ccfd7b320fb02e9348efca91333bf380c30eb83a88f - gitversion-linux-musl-arm64-6.0.5.tar.gz

... (truncated)

Changelog

Sourced from gitversion.tool's changelog.

v6.0.0

Platforms

• Drop support for .NET Framework 4.8, .NET Core 3.1 and .NET 5.0. Changed the project targets to .NET 6.0 or later.

Caching

• Refactor caching system in GitVersion to use json files instead of yaml files. This change is not backwards compatible with the old caching system.

Configuration changes:

• The configuration properties continuous-delivery-fallback-tag, tag-number-pattern, and tag were renamed to continuous-delivery-fallback-label, label-number-pattern, and label respectively. tag-pre-release-weight and tag-prefix remained as they were as they are referring to a Git tag.

• When using a commit message that matches both *-version-bump-message and no-bump-message, there is no increment for that commit. In other words, no-bump-message now takes precedence over *-version-bump-message.

• The fallback version strategy now returns 0.0.0 and is flagged with ShouldIncrement equal to true. This yields the version 0.1.0 on the develop branch (IncrementStrategy.Minor by default) and 0.0.1 on the main branch (IncremetnStrategy.Patch by default).

• The current branch (child) inherits its configuration from the source (parent) branch if the increment strategy is set to Inherit. This makes branch configuration recursive, simpler, more intuitive, more flexible, and more robust.

• Instead of having a single effective configuration, we now have one effective configuration per branch where the increment strategy is not set to inherit.

• The new implementation of the branch configuration inheritance affects per default only the pull-requests, hotfix and feature branches. In this case the next version will be generated like the child branch is not existing and the commits have been made on the source branch.

  • The following example illustrates this behavior. On the feature branch the semantic version 1.1.0-just-a-test.1+2 will now be generated instead of version 1.0.0-just-a-test.1+3 previously:

    * 1f1cfb4 52 minutes ago  (HEAD -> feature/just-a-test)
    * 1f9654d 54 minutes ago  (release/1.1.0)
    * be72411 56 minutes ago  (develop)
    * 14800ff 58 minutes ago  (tag: 1.0.0, main)
    

• A new unknown branch magic string has been introduced to give the user the possibility to specify the branch configuration for a branch which is not known. A branch is not known if only the regular expression of the branch configuration with the name unknown is matching. Please notice that this branch configuration behaves like any other branch configurations.

• Additional fallback branch configuration properties have been introduced at the root to define base properties which will be inherit to the branch configurations. That means if no other branch configuration in the inheritance line defines the given property the fallback property applies. Notice that the inheritance tree can be controlled using the increment strategy property in the branch configuration section.

  • The following example illustrates this behavior. The hotfix branch configuration overrides the main branch configuration and the result overrides the fallback branch configuration.

    * 1f1cfb4 52 minutes ago  (HEAD -> hotfix/just-a-test)
    * 14800ff 58 minutes ago  (tag: 1.0.0, main)
    

• When overriding the configuration with e.g. GitVersion.yaml the software distinguishes between properties who are not existent and properties who are null. This is especially important if the user wants to define branch related configuration which are marked with increment strategy Inherit.

• Following root configuration properties have been removed:

  • continuous-delivery-fallback-tag

• A new branch related property with name track-merge-message has been introduced. Consider we have a main branch and a release/1.0.0 branch and merge changes from release/1.0.0 to the main branch. In this scenario the merge message will be interpreted as a next version 1.0.0 when track-merge-message is set to true otherwise 0.0.1.

• The pre-release tags are only considered when they are matching with the label name of the branch. This has an effect on the way how the CommitCountSource will be determined.

... (truncated)

Commits

• 8856e30 update shipped API
• 1aefeed Merge pull request #4340 from arturcic/feature/filesystem
• e2734f8 fixing some warnings
• 012c377 Refactor MakeAndGetTempPath to use expression-bodied member
• 5147e95 Refactor file system operations to use IFileSystem interface
• 62f782f Fix repo setup logic in DynamicRepositoryTests
• 2305b7c removed TestFileSystem and usage
• e4c3745 Merge pull request #4339 from GitTools/dependabot/github_actions/crazy-max/gh...
• 0fecafc (build deps): Bump crazy-max/ghaction-setup-docker from 3 to 4
• fb71e8a Ignore specific version of LibGit2Sharp in Dependabot
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)