Skip to content

Commit db44df7

Browse files
committed
action.yml: list ucrt64 as a valid architecture value
The previous commits taught the implementation to handle `architecture: ucrt64`, but `action.yml` is what users (and the GitHub Actions tooling that renders the marketplace page and inlines the description into IDE tooltips) actually read. Extend the `architecture` input description to mention the new axis, and call out the caveat that only `flavor: full` is wired up end-to-end at this point, since `build-extra`'s `please.sh create-sdk-artifact` does not yet know about `--architecture=ucrt64` and there is no UCRT64 asset in the `ci-artifacts` release of `git-sdk-64`. Assisted-by: Opus 4.7 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
1 parent deaf4ae commit db44df7

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

action.yml

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,14 @@ inputs:
1111
default: 'minimal'
1212
architecture:
1313
required: false
14-
description: 'The architecture of the SDK: x86_64, i686 or aarch64. Note that "aarch64" only supports the "full" flavor for now.'
14+
description: >
15+
The architecture of the SDK: x86_64, i686, aarch64, or ucrt64.
16+
Note that "aarch64" only supports the "full" flavor for now.
17+
"ucrt64" selects the UCRT64 variant of git-sdk-64; while the
18+
MINGW64-to-UCRT64 migration is in progress it is cloned from a
19+
transitional "ucrt64" branch that will eventually replace "main",
20+
at which point "x86_64" itself will materialise a UCRT64 SDK.
21+
Only the "full" flavor is supported on the "ucrt64" axis for now.
1522
default: 'x86_64'
1623
msys:
1724
required: false

0 commit comments

Comments
 (0)