Skip to content

ci: publish GoReleaser drafts after artifact upload#5

Merged
intel352 merged 2 commits into
mainfrom
fix/goreleaser-draft-publish-flow
May 8, 2026
Merged

ci: publish GoReleaser drafts after artifact upload#5
intel352 merged 2 commits into
mainfrom
fix/goreleaser-draft-publish-flow

Conversation

@intel352
Copy link
Copy Markdown
Contributor

@intel352 intel352 commented May 8, 2026

Summary

  • configure GoReleaser to keep GitHub releases as drafts while artifacts are uploaded
  • publish the draft release only after the release workflow completes artifact/registry steps
  • keep release workflows compatible with GitHub immutable releases

Verification

  • actionlint on changed GoReleaser release workflow
  • git diff --check

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the release pipeline so GoReleaser creates GitHub releases as drafts, and the workflow explicitly publishes (undrafts) the release after GoReleaser completes—supporting artifact upload flows while staying compatible with GitHub’s immutable release behavior.

Changes:

  • Configure GoReleaser to create GitHub releases as drafts.
  • Add a workflow step to publish the draft GitHub release after the GoReleaser step succeeds.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.goreleaser.yaml Sets release.draft: true so GitHub releases are initially created as drafts.
.github/workflows/release.yml Adds a gh release edit ... --draft=false step to publish the draft release after GoReleaser finishes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@intel352 intel352 merged commit 870a5da into main May 8, 2026
8 checks passed
@intel352 intel352 deleted the fix/goreleaser-draft-publish-flow branch May 8, 2026 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants