[intel352]

Summary

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

Verification

• actionlint .github/workflows/release.yml
• git diff --check

[Copilot]

Pull request overview

This PR updates the release pipeline so GitHub Releases remain in draft state during artifact publication, and are only published at the end of the workflow to better align with GitHub’s immutable releases behavior.

Changes:

• Configure GoReleaser to create GitHub releases as drafts.
• Add a workflow step to publish (undraft) the release after the GoReleaser/artifact steps complete.

Reviewed changes

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

File	Description
.goreleaser.yml	Attempts to enable draft releases for GoReleaser (currently introduces a duplicate key conflict).
.github/workflows/release.yml	Adds a final step to publish the draft GitHub release via gh release edit.

Comments suppressed due to low confidence (1)

.goreleaser.yml:43

• release: block defines draft twice (draft: true and later draft: false). In YAML, the last key wins, so this configuration will still produce non-draft releases and the new workflow step becomes a no-op. Remove the duplicate and keep a single draft: true (or the intended value) under release:.

release:
  draft: true
  github:
    owner: GoCodeAlone
    name: workflow-plugin-security-scanner
  draft: false
  prerelease: false

---

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