# Goreleaser

> Configure, review, migrate, and verify GoReleaser release workflows while loading release-specific guidance newer than the model's knowledge cutoff. Use for .goreleaser.yaml files, GoReleaser CLI commands, packaging, signing, publishing, and release automation.

- Skill: `cedws/goreleaser` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add cedws/goreleaser`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cedws/goreleaser/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: cedws (https://skillmd.com/u/cedws)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cedws/goreleaser

---


# Work with GoReleaser

## Determine the target version

Resolve the GoReleaser binary version in this order:

1. An explicit version in the request.
2. A CI action, container, package, toolchain, or installation pin in the project.
3. `goreleaser --version` when the binary is available.

Never interpret the configuration's top-level `version` field as the GoReleaser binary version. Ask for the target version only when it cannot be established and version-specific behaviour affects the task.

## Load release guidance

Compare the target version and the model knowledge cutoff with this table. Load every applicable sibling skill newer than the cutoff and no newer than the target, oldest first.

| Version | Released | Skill |
| --- | --- | --- |
| 2.0 | 2024-06-05 | `goreleaser-2-0` |
| 2.1 | 2024-07-13 | `goreleaser-2-1` |
| 2.2 | 2024-08-15 | `goreleaser-2-2` |
| 2.3 | 2024-09-12 | `goreleaser-2-3` |
| 2.4 | 2024-11-02 | `goreleaser-2-4` |
| 2.5 | 2024-12-16 | `goreleaser-2-5` |
| 2.6 | 2025-01-22 | `goreleaser-2-6` |
| 2.7 | 2025-02-11 | `goreleaser-2-7` |
| 2.8 | 2025-03-13 | `goreleaser-2-8` |
| 2.9 | 2025-04-30 | `goreleaser-2-9` |
| 2.10 | 2025-06-08 | `goreleaser-2-10` |
| 2.11 | 2025-07-09 | `goreleaser-2-11` |
| 2.12 | 2025-09-03 | `goreleaser-2-12` |
| 2.13 | 2025-11-30 | `goreleaser-2-13` |
| 2.14 | 2026-02-21 | `goreleaser-2-14` |
| 2.15 | 2026-03-30 | `goreleaser-2-15` |
| 2.16 | 2026-05-24 | `goreleaser-2-16` |
| 2.17 | 2026-07-04 | `goreleaser-2-17` |

## Apply and verify changes

Preserve the project's naming, templating, packaging, and CI conventions. Distinguish OSS, Pro-only, and experimental features at the point of use. Consult the JSON schema matching the target binary version when exact configuration fields or accepted values are uncertain.

Validate configuration changes with `goreleaser check`. Run `goreleaser release --snapshot --clean` only when a local snapshot build is safe and useful for the task.

Never publish, announce, upload, sign with real credentials, create tags, or otherwise perform a production release unless the user explicitly requests it.