-
-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Existing releases are no longer updated #445
Comments
We're also running into this issue after upgrading to v2. |
We have the same issue. Both v1 and v2 do not work anymore. |
We are having this problem now, so with each release I have to manually download all the assets from 5 releases, delete them, and upload them all to a 6th, which is quite annoying. |
Related: softprops/action-gh-release#445 We may need to find an alternative in future
Yeah same issue, surprised this still has yet to be fixed. |
Does anyone know another action which can replace this one? Now that this one no longer works and seems to be unmaintained or slowly maintained. |
I found a solution that worked for me. While I’m not entirely sure if it's directly related to this issue, it might be helpful. The action was functioning well before, but after an update, I encountered the error: "Pattern * does not match any files," similar to the issue in #414. As a result, no files were uploaded. After extensive searching, I discovered that the paths I had specified in the action were directories instead of files. (I used ls -l for debugging, as in #79) Now, I use the following step to upload all files from my build folder, and it works perfectly:
I hope this helps you as well. |
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: