v2.0.0

Upgrade this GitHub Action to require Node.JS 24

Just like everybody else in the GitHub Actions ecosystem, we have to update
away from Node.js 20. This has been quite a bit of work!

Part of the effort, we switched away from Jest as the test framework, which has
only incomplete support for ES modules. The tests now run via vitest.

Thanks a ton to @Shadowghost for the invaluable support (and the prod 😉).

v1.12.0

Turn off caching by default

With this version, this GitHub Action no longer caches by default. To avoid
negative performance impact, the build-installers artifact is now downloaded
from the same rolling release as the minimal artifact.

Also: plenty of dependency updates, too many to list here.

v1.11.0

Optimize for the minimal flavor

As of git-for-windows/git-sdk-64#87, the
minimal flavor is published as an asset of a rolling GitHub Release.

This strikes a much better balance between generating and using the
artifact; Now, it is generated exactly once when an update is available,
and none of the users have to regenerate it.

The consequence is that no longer does setup-git-for-windows-sdk take
over a minute (uncached) to initialize the minimal Git for Windows SDK
(and only subsequent, cached calls would get to the desirable 2-5 second
range). Instead, the minimal Git for Windows SDK now consistently takes
2-5 seconds to initialize, no caching needed.

v1.10.4

Better support for architecture: aarch64

This release improves support for running on hosted windows-arm64
runners where Git for Windows needs to be installed as part of the
workflow.

v1.10.3

Lots of dependency updates & more stringent ci-artifacts query

This version brings tons and tons of updated dependencies, and is a bit
preciser when looking for the latest successful ci-artifacts run lest
it finds an accidentally-pushed topic branch that is not main.

v1.10.2

Really work around broken builds with GCC v14.1

A recent MSYS2 update upgraded GCC from v13.* to v14.*, for which Git's
source code is not prepared. v1.10.1 already aimed to work around this,
but only uncovered a long-standing bug preventing that work-around from
working correctly. v1.10.2 fixes that.

v1.10.1

Work around broken builds with GCC v14.1

A recent MSYS2 update upgraded GCC from v13.* to v14.*, for which Git's
source code is not prepared. Let's work around that for the time being.

v1.10.0

Now the result output is set to the path where the SDK is installed.

v1.9.0

This Action now uses node.js 20

v1.8.1

The Action no longer automatically force-enables symbolic link support

By mistake, a dependency of this Action defined
MSYS=winsymlinks:nativestrict, intending to fix the caching/restoring
but inadvertently causing a change in behavior of all workflows that use
this Action. This was fixed in the dependency, and by upgrading to a
newer version, the setup-for-windows-sdk Action is also fixed.