ci: Added CI/CD and release pipelines

[frol]

This is an initial setup taken from near.cli.rs. I will iterate from here.

[gemini-code-assist]

Summary of Changes

Hello @frol, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request establishes the foundational continuous integration and continuous delivery infrastructure for the ironclaw project. By integrating cargo dist and WiX installer definitions, it automates the build, testing, and release processes, significantly streamlining the distribution of the application across diverse operating systems and architectures.

Highlights

• CI/CD Pipeline Setup: Implemented initial CI/CD and release pipelines using cargo dist to automate building and distribution processes.
• Multi-platform Release Configuration: Configured cargo dist to generate installers for various platforms and formats, including shell, PowerShell, npm, and MSI for Windows, targeting multiple architectures (aarch64, x86_64) on Linux, macOS, and Windows.
• Windows Installer Definition: Introduced a WiX XML definition file (wix/main.wxs) to define the structure and components of the Windows MSI installer for the ironclaw application.

Changelog

• Cargo.toml
  • Added authors, homepage, and repository fields to package metadata.
  • Included package.metadata.wix section with upgrade-guid, path-guid, license, and eula settings.
  • Introduced profile.dist for release builds with LTO.
  • Configured workspace.metadata.dist for cargo-dist, specifying CI backend (github), installer types (shell, powershell, npm, msi), publish jobs (npm), and target platforms (aarch64/x86_64 for macOS, Linux, Windows).
  • Defined custom GitHub runners for specific target platforms.
• wix/main.wxs
  • Created a new WiX XML file defining the MSI installer for ironclaw.
  • Included product and package information, upgrade rules, and media definitions.
  • Set up directory structure for installation, including a bin folder for the executable.
  • Configured a component to add the application's binary to the system PATH.
  • Defined features for binaries and environment variable modification.
  • Included UI references and placeholders for EULA, banner, and dialog images.

Ignored Files

• Ignored by pattern: .github/workflows/** (4)
  • .github/workflows/code_style.yml
  • .github/workflows/release-plz.yml
  • .github/workflows/release.yml
  • .github/workflows/test.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces an initial CI/CD and release pipeline setup using cargo-dist and cargo-wix. The changes look like a great starting point. I've added a few suggestions to improve the user experience for different installers and to enhance the maintainability of the WiX installer configuration by using variables instead of hardcoded values.

[Copilot]

Pull request overview

This PR adds comprehensive CI/CD infrastructure for the ironclaw project, including GitHub Actions workflows for testing, code quality, releases, and automated package publishing. The configuration is based on the near.cli.rs project setup and includes multi-platform build support through cargo-dist.

Changes:

• Added GitHub Actions workflows for testing, code style checks, automated releases (release-plz), and multi-platform distribution (cargo-dist)
• Configured WiX installer for Windows MSI package generation
• Added cargo-dist metadata to Cargo.toml for managing releases across multiple platforms (Linux, macOS, Windows) with multiple architectures

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
.github/workflows/test.yml	Defines test workflow that runs on PRs and main branch pushes
.github/workflows/code_style.yml	Adds formatting and clippy linting checks on pull requests
.github/workflows/release-plz.yml	Automates version bumping and changelog generation on main branch
.github/workflows/release.yml	Auto-generated cargo-dist workflow for building and releasing multi-platform binaries
Cargo.toml	Adds package metadata, wix configuration, and cargo-dist settings for release automation
wix/main.wxs	WiX installer configuration for Windows MSI package generation

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[frol]

@ilblackdragon We need to configure the following secrets on the org or repo level:

• CARGO_REGISTRY_TOKEN for publishing and for users to install it from the source code via cargo install ironclaw
• NPM_TOKEN for npm install ironclaw / npx ironclaw (optional, but does not cost us anything, so I would just enable it)

[frol]

@ilblackdragon @serrrfirat Two tests fail, but that needs to be fixed in a separate PR.