chore(ci): 支持macOS构建与便携版exe

[YueerMoe]

Summary

• add macOS to build matrix for dev/preview/release workflows
• add cargo test step in CI
• produce and upload portable exe alongside NSIS installer; drop MSI target
• bundle targets updated to nsis+dmg+linux packages

Testing

• cargo test --manifest-path src-tauri/Cargo.toml
• yarn tauri build --bundles nsis

[gemini-code-assist]

Summary of Changes

Hello @YueerMoe, 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 significantly enhances the project's continuous integration and deployment capabilities by extending CI support to macOS and refining the build artifact generation. It streamlines the distribution process by adding a portable executable for Windows and explicitly defining cross-platform bundle targets, ensuring wider compatibility and easier deployment across various operating systems.

Highlights

• CI/CD Enhancements: The CI/CD pipeline has been updated to include macOS in the build matrix for development, preview, and release workflows, and a cargo test step has been added to ensure code quality.
• Windows Distribution: The Windows build process now produces and uploads a portable executable alongside the NSIS installer, while the MSI target has been removed to streamline distribution.
• Bundle Targets Configuration: The application's bundle targets have been explicitly defined in tauri.conf.json to include nsis, dmg, deb, rpm, and appimage, providing broader cross-platform distribution capabilities.

Changelog

• src-tauri/tauri.conf.json
  • Updated the bundle.targets configuration from the generic "all" to an explicit array: ["nsis", "dmg", "deb", "rpm", "appimage"]. This change specifies the exact bundle formats to be generated, enabling macOS .dmg bundles and other Linux formats.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/dev.yml
  • .github/workflows/preview.yml
  • .github/workflows/release.yml

Activity

• The pull request was created by YueerMoe.
• No further activity, such as comments or reviews, has been recorded since its creation.

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 updates the Tauri configuration to explicitly define build targets for Windows (NSIS), macOS (DMG), and Linux (deb, rpm, appimage), replacing the generic 'all' setting. This is a positive change for configuration clarity and control. I've suggested an improvement to further enhance the packaging by adding specific configurations for each target type to create more polished installers and packages.

[gemini-code-assist]

Great job on making the bundle targets explicit! This improves configuration clarity.

To further enhance the quality of the distributables, consider adding specific configuration for each target. This allows you to customize installers, define package dependencies, and set metadata for a more professional user experience.

For example, you can add deb, rpm, nsis, and dmg objects inside the bundle configuration:

"bundle": {
  // ...
  "targets": [...],
  "icon": [...],
  "deb": {
    "depends": [],
    "category": "Utility"
  },
  "nsis": {
    "license": "../LICENSE"
  }
  // ... etc.
}

You can find all available options in the Tauri configuration documentation.