Closed NobleDraconian closed 2 years ago
The release was just created and that triggers a jobs that builds the binaries. Then, we take those and attach them to the release so it should be resolved in just a few minutes 😄
It might be a better idea to create a draft release, and then attach the binaries to the draft. That way, when the release is actually published, things that rely on them downstream don't break!
Great idea, thanks for helping up improve the tool release process! :D
The very recent
v1.0.3
foreman release doesn't include binaries, which breaks any CI scripts that make use of foreman releases.