goreleaser-release-pipeline

Coordinate Release Please with GoReleaser v2 to publish versioned Go artifacts.

1|1|Updated May 3, 2026

Search Tags:#go #release #github-actions #tagging #ci #release-please #goreleaser

Ready to run

npx skills add https://github.com/matt-riley/agent-skills --skill goreleaser-release-pipeline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: goreleaser-release-pipeline
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/goreleaser-release-pipeline
Command: npx skills add https://github.com/matt-riley/agent-skills --skill goreleaser-release-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables reliable integration of Release Please with a GoReleaser v2 release flow, ensuring tags, GitHub releases, and publish jobs coordinate so versioned releases and assets are not lost.

Core Features & Use Cases

Align Release Please with GoReleaser v2 in a single workflow to publish binaries and assets on release.
Gate the publish job on the release_created output to prevent releases without assets or failed publish steps.
Diagnose and fix tag formats, publish conditions, and workflow wiring without redesigning the entire CI.

Quick Start

Set up a single workflow that runs Release Please for Go, gates the GoReleaser publish step on the release_created output, and uses plain semver tags.

Frequently Asked Questions about goreleaser-release-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate Release Please with GoReleaser to publish Go binaries?▼

Coordinate Release Please with GoReleaser by setting up a single GitHub Actions workflow that gates the GoReleaser publish step on the release_created output, ensuring binaries and assets publish only when a release is actually created.

Why does my GoReleaser publish job run without uploading release assets?▼

Your GoReleaser publish job likely lacks gating on the release_created output. Gate the publish step with this output to prevent empty GitHub releases or failed publish steps when Release Please has not created a new release.

What tag format does GoReleaser v2 require when integrating with Release Please?▼

GoReleaser v2 requires plain semver tags when integrating with Release Please. Synchronize the tag formats between both tools to ensure versioned Go artifacts and GitHub releases are not lost during the CI workflow.

Does GoReleaser need full git history for publishing Go releases in GitHub Actions?▼

Yes, GoReleaser requires a full checkout with fetch-depth: 0. Setting the GitHub Actions checkout fetch-depth to 0 ensures GoReleaser can access the complete git history needed to generate changelogs and publish versioned artifacts.

Can I fix Release Please and GoReleaser workflow wiring without redesigning my CI?▼

Yes, you can diagnose and fix tag formats, publish conditions, and workflow wiring without redesigning the entire CI pipeline. Align Release Please with GoReleaser v2 in a single workflow to synchronize tag formats and asset publishing.