fix goreleaser.yaml

[syx0310]

Summary by CodeRabbit

• New Features

  • Enhanced configuration for versioning and build specifications, now supporting arm64 architecture and specific ARM versions.
  • Improved naming conventions for generated archives and checksum files for better clarity.

• Bug Fixes

  • Updated naming templates to ensure consistency across different sections of the configuration.

• Documentation

  • Expanded documentation to reflect changes in the configuration schema and enhancements in architecture support.

[coderabbitai]

Walkthrough

The changes to the configuration enhance the .goreleaser.yaml file by upgrading to version 2, expanding support for various architectures, and improving output clarity. Key modifications include detailed naming templates for archives and checksums, aligning the structure across sections. This update fosters a more robust configuration system, accommodating a wider range of platforms while simplifying file identification for users.

Changes

Files	Change Summary
.goreleaser.yaml	Upgraded to version: 2, modified name_template to version_template, expanded builds for arm64, and updated naming conventions for archives and checksums for clarity and consistency.

Poem

In fields of code where rabbits roam,
We've tweaked our files to feel like home.
With builds that leap and names so bright,
Our releases shine, a joyous sight! 🐇✨
So hop along, both far and near,
The changes made, let's all cheer! 🎉

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6c16fdc and c051da8.

Files selected for processing (1)

• .goreleaser.yaml (3 hunks)

Additional comments not posted (5)

.goreleaser.yaml (5)

14-17: Enhanced architecture support.

The addition of arm64 and specific ARM versions (6 and 7) improves compatibility with more platforms.

---

19-27: Improved archive naming clarity.

The restructured naming template provides better clarity and detail, making it easier to identify target architectures.

---

31-31: Consistent versioning scheme for snapshots.

The version_template for snapshots aligns with the new versioning scheme, maintaining consistency.

---

62-69: Consistent naming conventions in nfpms.

The file_name_template in the nfpms section mirrors the archive section, ensuring consistent naming conventions.

---

1-1: Verify compatibility with version 2.

Updating the version to 2 suggests a major schema change. Ensure that all features used are compatible with this version and check for any deprecated features.