ci: re-enable Windows builds in Tauri release workflow

[Yana-do-code]

Re-adds Windows platform to the build matrix after it was previously disabled in commit 9f8eaf1. This restores multi-platform build support for Windows alongside macOS (Intel/Apple Silicon) and Linux.

The workflow will now generate Windows installers:

• .msi (Windows Installer Package)
• .exe (NSIS-based installer)

All necessary Windows configuration is already in place:

• icon.ico exists in src-tauri/icons/
• Artifact upload paths configured for both msi and nsis
• Cross-platform build commands using npx cross-env

Also the simulator works fine in local server .

Summary by CodeRabbit

• Chores
  • Enhanced build system infrastructure to support Windows platform builds in the automated release pipeline.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

✅ Deploy Preview for circuitverse ready!

Name	Link
🔨 Latest commit	f071ead
🔍 Latest deploy log	https://app.netlify.com/projects/circuitverse/deploys/695e4556e0a7330008ead262
😎 Deploy Preview	https://deploy-preview-730--circuitverse.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 44 (🟢 up 22 from production) Accessibility: 73 (no change from production) Best Practices: 92 (no change from production) SEO: 82 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

This pull request modifies the .github/workflows/tauri-release.yml GitHub Actions workflow to add Windows as a build target in the job matrix configuration. A new matrix item is inserted with platform: 'windows-latest' and empty build arguments. This enables the CI pipeline to execute release builds on Windows infrastructure without altering existing build steps or platform-specific handling logic.

Possibly related PRs

• Update Tauri release workflow for additional branch and paths #716: Modifies the same workflow file's matrix configuration formatting and entries
• CI: Establishing an Automated Release Pipeline for Streamlined Deployment #503: Adds Windows as a target operating system in the same workflow's build matrix

🚥 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 'ci: re-enable Windows builds in Tauri release workflow' directly and clearly summarizes the main change: re-enabling Windows builds in a CI workflow.
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

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f071795 and f071ead.

📒 Files selected for processing (1)

• .github/workflows/tauri-release.yml

🔇 Additional comments (1)

.github/workflows/tauri-release.yml (1)

24-25: Approve—verify Windows builds succeed in CI before merging.

The Windows matrix entry correctly follows the established pattern and aligns with the configured artifact paths (.msi and .exe bundles on lines 84-85). WebView2 is pre-installed on windows-latest runners, so no additional setup is required. Since Windows builds were previously disabled, run this workflow on the PR to confirm the build completes successfully on Windows CI.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[Yana-do-code]

@tachyons

[Yana-do-code]

@senbo1 Please review it.

[ThatDeparted2061]

Thanks for the contribution but the windows build was failing that is why we didnt add it. Rather it will be better if you investigate the reason for that.