operator-lifecycle-manager icon indicating copy to clipboard operation
operator-lifecycle-manager copied to clipboard

Published 20 hours ago • verified publisher icon operator-framework

GORELEASER GitHub Action resulted in two Draft Releases

Open awgreene opened this issue 1 year ago • 2 comments

Bug Report

@tmshort pushed a v0.26.0 tag which triggered the goreleaser GitHub Workflow which for some reason created two v0.26.0 Draft Releases. The 10 expected assets were split between these two Draft Releases.

What did you do?

  1. Checkout out the master branch
  2. Pulled changes
  3. Tagged the branch as v0.26.0
  4. Pushed the tag
  5. Waited for the goreleaser GH Workflow to complete
  6. Visited https://github.com/operator-framework/operator-lifecycle-manager/releases and found two v0.26.0 Draft Releases. The 10 assets expected with a release were split between these two drafts.

What did you expect to see? A single v0.26.0 release with all 10 of the expected assets.

What did you see instead? Under which circumstances? Two v0.26.0 Draft Releases. The 10 assets expected with a release were split between these two drafts.

awgreene avatar Oct 31 '23 18:10 awgreene

Were the release note text (or anything else) different?

tmshort avatar Oct 31 '23 18:10 tmshort

Only one of the Draft PRs had commit messages / notes

awgreene avatar Oct 31 '23 19:10 awgreene