v1.6.2

Use https://github.com/git-for-windows/git-sdk-arm64 in ARM64 mode

This turns out to be much faster than using git-sdk-64 and calling
Pacman to install the packages.

v1.6.1

Support more flavors in ARM64 mode

v1.6.0

Work around API rate limits

This version works around error messages like this one:

Error: API rate limit exceeded for 172.176.196.48. (But here's the
good news: Authenticated requests get a higher rate limit. Check out
the documentation for more details.)

v1.5.2

Avoid cluttering the workflow runs' summary page

No need to report the commit or output location more prominently than in the actual step's log that uses this Action.

v1.5.1

Better support for self-hosted runners

This version comes with support for self-hosted runners that do not have Git for Windows installed.

This version also addresses the warning about using the deprecated workflow command save-state.

v1.5.0

This version introduces support for (self-hosted) Windows/ARM64

There is a convenient Azure Resource Manager template to easily set up a Windows/ARM64 VM on Azure and register it as a self-hosted runner for GitHub Actions.

With this version of setup-git-for-windows-sdk, it is possible to target such runners by configuring the architecture to aarch64. This
will install a hybrid SDK: most of the base packages are x86_64 ones and will run using Windows 11's emulation. But the clang toolchain is
fully aarch64 and ready to build aarch64 executables, too.

Better support for self-hosted runners

By configuring cleanup: true for this Action, the SDK that is set up will automatically be torn down at the end of the GitHub workflow run.

v1.4.2

Let's clean up .tmp once the SDK was initialized successfully.

v1.4.1

Avoid using git.exe from the current directory, if there is any

v1.4.0

Let's use partial clone/parallel checkout even for the minimal flavor!

v1.3.0

Let's use partial clone/parallel checkout whenever possible!