Skip to content
This repository was archived by the owner on Mar 5, 2026. It is now read-only.

feat: add Windows release binaries to CI pipeline#18

Merged
andersonleal merged 2 commits intomainfrom
feat/windows-ci
Feb 23, 2026
Merged

feat: add Windows release binaries to CI pipeline#18
andersonleal merged 2 commits intomainfrom
feat/windows-ci

Conversation

@andersonleal
Copy link
Copy Markdown
Contributor

@andersonleal andersonleal commented Feb 20, 2026

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

  • Feature — Adds Windows release binaries to the CI/CD pipeline
  • Bug fix
  • Refactor
  • Documentation
  • Other

Changes

.github/workflows/release.yml

  • Added 3 Windows targets to the build matrix: x86_64-pc-windows-msvc, i686-pc-windows-msvc, aarch64-pc-windows-msvc (all on windows-latest)
  • Added zip: windows to taiki-e/upload-rust-binary-action for Windows artifact packaging
  • Updated Slack notification binary counts from 5 to 8 across all status messages

.github/workflows/validate-release.yml

  • Added the same 3 Windows targets to the validation TARGETS array
  • Updated validation success message from "5 platform binaries" to "8 platform binaries"

Checklist

  • Code follows project conventions
  • Changes are limited to CI/CD workflows (release and validate-release)
  • No new dependencies introduced
  • Slack notifications updated to reflect new binary count

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. The taiki-e/upload-rust-binary-action with zip: windows produces .zip archives for Windows targets instead of .tar.gz.

Summary by CodeRabbit

Release Notes

  • New Features

    • Extended platform support to include Windows x86_64, i686, and aarch64 architecture binaries
  • Chores

    • Enhanced release workflow with dynamic target count system for flexible multi-platform releases
    • Improved binary artifact validation and Slack notification messaging
    • Added Windows-specific cross-compilation verification

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 23, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 258cf8c and 85ae71c.

📒 Files selected for processing (2)
  • .github/workflows/release.yml
  • .github/workflows/validate-release.yml

📝 Walkthrough

Walkthrough

The 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

Cohort / File(s) Summary
CI/CD Workflow Updates
.github/workflows/release.yml, .github/workflows/validate-release.yml
Both workflows updated to support Windows build targets (x86_64-pc-windows-msvc, i686-pc-windows-msvc, aarch64-pc-windows-msvc). Hard-coded target counts ("5") replaced with dynamic references (TOTAL_TARGETS environment variable or array length). Release workflow adds Windows-specific verification step and artifact handling configuration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Hops with delight through the CI streams,
Windows targets joined the building dreams!
No more fixed numbers, now we count true,
Dynamic variables make workflows new!
Eight platforms strong, the pipeline gleams!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'feat: add Windows release binaries to CI pipeline' directly and accurately describes the main change—adding Windows binary builds to the CI pipeline.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/windows-ci

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


Comment @coderabbitai help to get the list of available commands and usage tips.

@andersonleal andersonleal merged commit 0f40f5b into main Feb 23, 2026
1 check passed
@andersonleal andersonleal deleted the feat/windows-ci branch February 23, 2026 13:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant