ci: Use native platform for win-cross task
What changed, and why it matters
This commit removes a single line from a Bitcoin Core continuous integration (CI) configuration file. The removed line forced the Windows cross-compilation CI task to run on the linux/amd64 platform. After the change, the CI task will use the CI runner's native platform instead. This is a build-infrastructure tweak with no apparent effect on the Bitcoin Core software that end users run.
No security action required. Treat as a normal CI/maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In ci/test/00_setup_env_win64.sh, the line export CI_IMAGE_PLATFORM="linux/amd64" is deleted. This environment variable previously pinned the Docker image platform for the Windows cross-compile CI job to amd64. Removing it lets the CI system default to the host’s native platform. The change is purely in CI orchestration and does not modify source code, build scripts, consensus logic, networking, wallet handling, or any shipped binary.
Changed components
ci/test/00_setup_env_win64.shInspect captured patch +0 / −1
diff --git a/ci/test/00_setup_env_win64.sh b/ci/test/00_setup_env_win64.sh
index 13e794bd..f929f34c 100755
--- a/ci/test/00_setup_env_win64.sh
+++ b/ci/test/00_setup_env_win64.sh
@@ -8,7 +8,6 @@ export LC_ALL=C.UTF-8
export CONTAINER_NAME=ci_win64
export CI_IMAGE_NAME_TAG="mirror.gcr.io/ubuntu:24.04" # Check that https://packages.ubuntu.com/noble/g++-mingw-w64-x86-64-posix (version 13.x, similar to guix) can cross-compile
-export CI_IMAGE_PLATFORM="linux/amd64"
export HOST=x86_64-w64-mingw32
export PACKAGES="g++-mingw-w64-x86-64-posix nsis"
export RUN_UNIT_TESTS=false
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.