Open
Description
Description
When I run Rust's bindgen on windows-latest, sometimes the reported version is 18.1 and sometimes it's 19.
The bindgen tool fails with:
Failed to generate bindings: ClangDiagnostic("C:\\Program Files\\Microsoft Visual Studio\\2022\\Enterprise\\VC\\Tools\\MSVC\\14.44.35207\\include\\yvals_core.h:908:1: error: static assertion failed: error STL1000: Unexpected compiler version, expected Clang 19.0.0 or newer.\n")
because the headers in MSVC are newer than the last supported version of clang. This started sporadically breaking recently.
Platforms affected
- Azure DevOps
- GitHub Actions - Standard Runners
- GitHub Actions - Larger Runners
Runner images affected
- Ubuntu 22.04
- Ubuntu 24.04
- macOS 13
- macOS 13 Arm64
- macOS 14
- macOS 14 Arm64
- macOS 15
- macOS 15 Arm64
- Windows Server 2019
- Windows Server 2022
- Windows Server 2025
Image version and build link
No public example
Is it regression?
Yes. Works: https://github.com/actions/runner-images/blob/win22/20250609.2/images/windows/Windows2022-Readme.md Broken: https://github.com/actions/runner-images/blob/win22/20250617.1/images/windows/Windows2022-Readme.md
Expected behavior
The build capability shouldn't have regressed & bindgen should still be working.
Actual behavior
Bindgen is failing
Repro steps
windows-latest seems to be inconsistent about the image it's selecting (maybe incremental rollout?) and sometimes it's picking a broken image.