fix goreleaser warnings

[kradalby]

Summary by CodeRabbit

• New Features
  • Updated versioning scheme to version 2 for improved release management.
  • Enhanced snapshot versioning with a new naming template for better clarity.

[coderabbitai]

Walkthrough

The changes to the .goreleaser.yml configuration file introduce a new versioning scheme by adding a version key set to 2. Additionally, the name_template key in the snapshot section has been renamed to version_template, altering how versioning for snapshots is defined. These modifications impact the overall structure of version information within the release process.

Changes

Files	Change Summary
.goreleaser.yml	Added version: 2 and changed name_template to version_template

Poem

In the meadow, hops a clever hare,
With changes bright, we dance with flair.
Version two, a leap so grand,
Templates shift, a new command.
Let’s celebrate with joy and cheer,
For every hop brings progress near! 🐇✨

---

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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 35bfe7c and 3ed9184.

Files selected for processing (1)

• .goreleaser.yml (2 hunks)

Additional comments not posted (2)

.goreleaser.yml (2)

2-2: Verify compatibility with GoReleaser version.

The addition of version: 2 at line 2 suggests a significant change in the configuration schema. It's crucial to ensure that this version is compatible with the installed GoReleaser version to avoid runtime issues.

Please confirm that the GoReleaser version in use supports the version: 2 configuration schema. This can typically be checked in the GoReleaser release notes or documentation.

---

188-188: Update to version template in snapshots is appropriate.

The change from name_template to version_template at line 188 correctly reflects the intended use of versioning in snapshot releases. This change should help clarify the purpose and usage of the template in defining snapshot versions.