Fix GoReleaser v2 config schema

[skyoo2003]

Summary

• brews.tap → brews.repository (removed in GoReleaser v2)
• brews.folder → brews.directory (removed in GoReleaser v2)
• dockers → dockers_v2 (new v2 Docker config section)

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the GoReleaser configuration to match v2 schema changes for Homebrew taps and Docker definitions.

File-Level Changes

Change	Details	Files
Align GoReleaser Homebrew and Docker configuration with v2 schema fields.	Rename Homebrew brew tap configuration field from tap to repository and keep owner/name/token nested under it Rename Homebrew brew output directory field from folder to directory Rename top-level dockers configuration section to dockers_v2 while keeping existing image and dockerfile settings	.goreleaser.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path=".goreleaser.yml" line_range="79-82" />
<code_context>
   skip_upload: false

-dockers:
+dockers_v2:
 - images:
   - ghcr.io/skyoo2003/kvs
   dockerfile: Dockerfile.goreleaser
</code_context>
<issue_to_address>
**issue (bug_risk):** The `dockers_v2` key is likely invalid and will be ignored by GoReleaser.

GoReleaser only recognizes `dockers` (and `docker_manifests`) as top-level keys; `dockers_v2` is not part of the schema, so this block will be ignored. Rename it to `dockers` and, if you intend to use the v2 Docker builder, update the nested fields accordingly so your images are actually built and published.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (bug_risk): The dockers_v2 key is likely invalid and will be ignored by GoReleaser.

GoReleaser only recognizes dockers (and docker_manifests) as top-level keys; dockers_v2 is not part of the schema, so this block will be ignored. Rename it to dockers and, if you intend to use the v2 Docker builder, update the nested fields accordingly so your images are actually built and published.