feat: add Windows release binaries to CI pipeline#18
Conversation
…and adjust binary count
…and improve validation messages
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe CI/CD workflows are updated to support Windows build targets alongside existing platforms. A dynamic TOTAL_TARGETS environment variable replaces hard-coded numeric references across Slack notifications and status messages. The release workflow adds three Windows target variants and Windows-specific verification and artifact handling steps. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Comment |
Summary
Add Windows binary builds to the iii-console release pipeline. The release workflow now produces 8 platform binaries (up from 5), including three Windows targets: x86_64, i686, and aarch64 (MSVC toolchain), matching the iii-engine's Windows support.
Type of Change
Changes
.github/workflows/release.ymlx86_64-pc-windows-msvc,i686-pc-windows-msvc,aarch64-pc-windows-msvc(all onwindows-latest)zip: windowstotaiki-e/upload-rust-binary-actionfor Windows artifact packaging.github/workflows/validate-release.ymlChecklist
Additional Context
Implements the plan in
docs/plans/2026-02-20-windows-release-binaries.md. Windows builds use the same frontend artifact from the Ubuntu build step; no cross-compilation tools are needed on Windows runners since the MSVC toolchain is native. Thetaiki-e/upload-rust-binary-actionwithzip: windowsproduces.ziparchives for Windows targets instead of.tar.gz.Summary by CodeRabbit
Release Notes
New Features
Chores