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
Issue publishing new release on v1.9.0 #3115
Comments
Hey! |
everyone using draft releases, right? probably #3073 |
One thing I just realized about this is that it won't actually work as the artifacts from the previous release will still be there and have the same name... this will likely require more work, so I'll revert both the fix and original change, at least for now. |
Will there be a patch release with this included in the next day or two? |
yes, today probably |
released! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
I went to publish a new version (v0.5.0) of
osv-detector
and it failed right at the end when trying to push the release to github:I tried restarting the build, and with a new tag (v0.5.1) just in case it was being thrown off by the release & tag previously being drafted and then deleted (which I think I did for v0.5.0, but can't remember so I tried a new tag just incase).
I've not changed anything in my GitHub profile or repository - the only difference I knew of between these runs and the last release (which was a month ago) was that that run was using v1.8.3, and these runs were using v1.9.0.
So I pinned
goreleaser
to v1.8.3 (G-Rath/osv-detector#97) and that was successful: https://github.com/G-Rath/osv-detector/runs/6513592978?check_suite_focus=trueHow can we reproduce this?
I don't know for sure - hopefully it will be enough to use my actions workflow:
goreleaser version
GoReleaser Check
Search
Code of Conduct
Additional context
Looking over the changelogs, the main change that jumped out at me was that
go-github
was updated from v43 to v44.The text was updated successfully, but these errors were encountered: