Skip to content

ci: enable Windows in third-party-tests matrix - #89

Draft
o-nnerb wants to merge 2 commits into
mainfrom
ci/enable-windows-third-party-tests
Draft

ci: enable Windows in third-party-tests matrix#89
o-nnerb wants to merge 2 commits into
mainfrom
ci/enable-windows-third-party-tests

Conversation

@o-nnerb

@o-nnerb o-nnerb commented Aug 5, 2026

Copy link
Copy Markdown
Member

Summary

  • Uncomments the windows-latest leg of the third-party-tests matrix in the reusable swift-ci.yaml workflow. The Windows-specific coverage-move step (pwsh) and setup-swift version input were already in place — only the matrix entry itself was disabled.
  • SwiftyLab/setup-swift officially supports windows-latest runners (its only caveat is no toolchain caching on Windows for Swift ≥5.10, which doesn't apply here since caching isn't used).

Test plan

  • Merge into main and confirm a caller repo (e.g. request-dl-nio, which pulls @main) picks up the Windows leg on its next CI run
  • Confirm swift test --enable-code-coverage actually builds/runs on windows-latest for a real package (first real-world validation of Windows support for this reusable workflow — dependencies like swift-nio-ssl/swift-nio-transport-services haven't been exercised on Windows in this org before)
  • If the build fails on Windows-specific dependency issues, re-comment the matrix entry or gate it behind an opt-in input

🤖 Generated with Claude Code

https://claude.ai/code/session_014J3dTN4EzK6D1hokyfeAHU

o-nnerb added 2 commits August 5, 2026 20:34
The Windows leg (setup-swift + pwsh coverage-move step) was already
scaffolded but left commented out; SwiftyLab/setup-swift officially
supports windows-latest runners, so turn it on.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant