Skip to content

ci: publish GoReleaser drafts after artifact upload - #3

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

intel352 merged 2 commits into
mainfrom
fix/goreleaser-draft-publish-flow

Conversation

@intel352

@intel352 intel352 commented May 8, 2026

Copy link
Copy Markdown
Contributor

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

Copilot AI left a comment

Copy link
Copy Markdown

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 adjusts the release pipeline so GoReleaser creates GitHub releases as drafts during artifact upload, then the workflow explicitly publishes the release once the job completes—helping avoid issues with GitHub “immutable releases” semantics.

Changes:

  • Configure GoReleaser to create GitHub releases as drafts.
  • Add a workflow step to publish (unset draft) after GoReleaser 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 releases remain drafts during asset upload.
.github/workflows/release.yml Publishes the draft release at the end of the workflow via gh release edit.

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

@intel352
intel352 merged commit feda29f into main May 8, 2026
9 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