Bot releases are visible (Hide)
Published by github-actions[bot] about 1 month ago
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.
Published by github-actions[bot] about 2 months ago
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
.
Published by github-actions[bot] 5 months ago
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.
Published by github-actions[bot] 5 months ago
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.
Published by github-actions[bot] 10 months ago
Now the result
output is set to the path where the SDK is installed.
Published by github-actions[bot] 12 months ago
This Action now uses node.js 20
Published by github-actions[bot] over 1 year ago
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.
Published by github-actions[bot] over 1 year ago
Add support for Windows/ARM64
With this release, the GitHub Action adds full support for Windows/ARM64. While previously only the full
flavor was supported, now the minimal
, makepkg-git
and build-installers
flavors are also supported.
Note: As of time of writing, there is no support for hosted Windows/ARM64 runners, but it is possible to self-host such runners.
Published by github-actions[bot] almost 2 years ago
Use faster D: drive, if available
Published by github-actions[bot] almost 2 years ago
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.
Published by github-actions[bot] almost 2 years ago
Support more flavors in ARM64 mode
Published by github-actions[bot] almost 2 years ago
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.)
Published by github-actions[bot] almost 2 years ago
No need to report the commit or output location more prominently than in the actual step's log that uses this Action.
Published by github-actions[bot] almost 2 years ago
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
.
Published by github-actions[bot] about 2 years ago
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.
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.
Published by github-actions[bot] over 2 years ago
Let's clean up .tmp
once the SDK was initialized successfully.
Published by github-actions[bot] over 2 years ago
Avoid using git.exe
from the current directory, if there is any
Published by github-actions[bot] over 2 years ago
Let's use partial clone/parallel checkout even for the minimal
flavor!
Published by github-actions[bot] over 2 years ago
Let's use partial clone/parallel checkout whenever possible!
Published by github-actions[bot] over 2 years ago
Let's use Node v16!