You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a workflow where we create a draft release, then upload binaries (by OS) in a matrix, then publish the release. This action is creating a new release in the last step, instead of updating draft to false.
In publish, it creates the draft release as expected.
In upload, it finds the draft release and attaches the binaries to it as expected.
But in publish, it doesn't find the draft release, it creates a new one.
I'm particularly confused why upload works correctly, but publish does not.
// you can't get a an existing draft by tag// so we must find one in the list of all releasesif(config.input_draft){
The action will only find a draft release if input_draft. This means passing draft: true is the only way to find/update a draft release, which makes it kind of hard when you want to update it to draft: false! I think this is different from the Issues and PRs linked above -- at least, neither of the PRs seem to change this line to correct this behavior.
We have a workflow where we create a draft release, then upload binaries (by OS) in a matrix, then publish the release. This action is creating a new release in the last step, instead of updating
draft
tofalse
.In publish, it creates the draft release as expected.
In upload, it finds the draft release and attaches the binaries to it as expected.
But in publish, it doesn't find the draft release, it creates a new one.
I'm particularly confused why upload works correctly, but publish does not.
There seems to be a few Issues,
And PRs,
In this area, but they're all multiple years old (is this action still maintained?), so I don't know if they're still applicable.
The text was updated successfully, but these errors were encountered: