ci-artifacts: add workflow for the build-installers artifact#55
Merged
Conversation
This ports a subset of the `ci-artifacts` workflow from git-sdk-64 (see git-for-windows/git-sdk-64#113) to git-sdk-32. Since git-sdk-32 does not build a minimal SDK artifact, only the `build-installers` flavor is included. On every push to `main`, the workflow creates a `build-installers` SDK artifact via `please.sh create-sdk-artifact`, compresses it as `git-sdk-i686-build-installers.tar.zst`, and publishes it to a rolling `ci-artifacts` GitHub release. The publish step uses the same temporary-rename strategy as git-sdk-64 to minimize the window during which the asset is unavailable. Assisted-by: Claude Opus 4.6 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
mjcheetham
approved these changes
Apr 22, 2026
dscho
added a commit
to Shadowghost/setup-git-for-windows-sdk
that referenced
this pull request
Apr 27, 2026
As of git-for-windows/git-sdk-64#113, git-for-windows/git-sdk-arm64#56 and git-for-windows/git-sdk-32#55, the `ci-artifacts` releases of the git-sdk-* repositories now provide pre-built `build-installers` artifacts as `.tar.zst` files (e.g. `git-sdk-x86_64-build-installers.tar.zst`). Downloading and extracting these is substantially faster than the previous approach of cloning the repository and running `please.sh create-sdk-artifact`. The built-in `tar.exe` on Windows Server 2025 and Windows 11 24H2 (OS build 26100 and later) supports Zstandard decompression natively via libarchive (which is the reason why above-mentioned PRs use that format to publish the `build-installers` artifact). Older runner images such as `windows-2022` (build 20348) lack this support, so we detect the OS build number at runtime and fall back to the existing `getViaGit` code path when Zstandard extraction would fail. The `getViaCIArtifacts` function now accepts a `flavor` parameter so both `minimal` (which continues to use `.tar.gz`) and `build-installers` (which uses `.tar.zst`) can be served from the same code path with hardcoded, per-flavor asset names that match the actual release assets. Assisted-by: Claude Opus 4.6 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This ports a subset of the
ci-artifactsworkflow from git-sdk-64 (see git-for-windows/git-sdk-64#113) to git-sdk-32. Since git-sdk-32 does not build a minimal SDK artifact, only thebuild-installersflavor is included.On every push to
main, the workflow creates abuild-installersSDK artifact viaplease.sh create-sdk-artifact, compresses it asgit-sdk-i686-build-installers.tar.zst, and publishes it to a rollingci-artifactsGitHub release.