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
This used to just update the existing release with the new files (adding one by one as they are built), noticed recently, that isn't the case anymore. I've been getting Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
Looking at the changes, I think the problem lies in #386 although don't know exactly what, likely octokit is adding something more to the request causing this to fail. Or more likely doing some pre-flight checks like "does the tag exist?".
Trying the commit right before this one, seems to have helped my workflow to work again.
I currently use a matrix to generate jobs, each has the same payload just different file when creating a release.
https://github.com/debdutdeb/novm/blob/cf13d8741fee6959d72dd8bae05cdb5750ca30e9/.github/workflows/release.yaml#L20-L44
This used to just update the existing release with the new files (adding one by one as they are built), noticed recently, that isn't the case anymore. I've been getting
Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
Looking at the changes, I think the problem lies in #386 although don't know exactly what, likely octokit is adding something more to the request causing this to fail. Or more likely doing some pre-flight checks like "does the tag exist?".
Trying the commit right before this one, seems to have helped my workflow to work again.
commit
your commit
workflow result
The text was updated successfully, but these errors were encountered: