Action tries to make a new release when one already exists
See original GitHub issueI use action-gh-release
to automatically upload a CI build when a new release is cut. Recently this has stopped working. It looks like the action is trying to make the release, even though it already exists.
release:
needs: build
runs-on: ubuntu-latest
if: ${{ github.event_name == 'release'}}
permissions:
contents: write
steps:
- uses: actions/download-artifact@v2
with:
name: totsugeki
- uses: softprops/action-gh-release@v1
with:
files: totsugeki.exe
https://github.com/optix2000/totsugeki/runs/3275313508?check_suite_focus=true
Run softprops/action-gh-release@v1
👩🏭 Creating new GitHub release for tag v1.1.3...
⚠️ GitHub release failed with status: 422, retrying... (2 retries remaining)
👩🏭 Creating new GitHub release for tag v1.1.3...
⚠️ GitHub release failed with status: 422, retrying... (1 retries remaining)
👩🏭 Creating new GitHub release for tag v1.1.3...
⚠️ GitHub release failed with status: 422, retrying... (0 retries remaining)
❌ Too many retries. Aborting...
Error: Too many retries.
Compared to previously: https://github.com/optix2000/totsugeki/runs/3268658767?check_suite_focus=true
Run softprops/action-gh-release@v1
⬆️ Uploading totsugeki.exe...
Deprecation: [@octokit/rest] "file" parameter is deprecated for ".repos.uploadReleaseAsset()". Use "data" instead
at /home/runner/work/_actions/softprops/action-gh-release/v1/dist/index.js:1:437047
at Array.forEach (<anonymous>)
at Object.s [as uploadReleaseAsset] (/home/runner/work/_actions/softprops/action-gh-release/v1/dist/index.js:1:436958)
at /home/runner/work/_actions/softprops/action-gh-release/v1/dist/index.js:1:52043
at Generator.next (<anonymous>)
at /home/runner/work/_actions/softprops/action-gh-release/v1/dist/index.js:1:50565
at new Promise (<anonymous>)
at i (/home/runner/work/_actions/softprops/action-gh-release/v1/dist/index.js:1:50313)
at Object.t.upload (/home/runner/work/_actions/softprops/action-gh-release/v1/dist/index.js:1:51907)
at /home/runner/work/_actions/softprops/action-gh-release/v1/dist/index.js:1:44485 {
name: 'Deprecation'
}
🎉 Release ready at https://github.com/optix2000/totsugeki/releases/tag/v1.1.2
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:5 (3 by maintainers)
Top Results From Across the Web
An Action to create releases via the GitHub Release API
This will create a Release, as well as a release event, which could be handled by a third party service, or by GitHub...
Read more >Remote Origin Already Exists Error: How To Fix It | CloudBees
1. Remove the Existing Remote · Create a new repository online using GitHub or GitLab. · Go to your local repository and remove...
Read more >"Updates were rejected because the tag already exists" when ...
The reason this is common in SourceTree is because the Push all tags option is set to on by default. (Another way to...
Read more >Failed to register bundle identifi… | Apple Developer Forums
I think the problem is that Xcode is trying to create a new identifier automatically on your behalf, but the identifier already exists...
Read more >How to fix 'fatal: remote origin already exists' Git error - Komodor
This will give you room to add a new origin to the list of attached handlers. So when you run git remote add...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think I can see that regression in this pull request
https://github.com/softprops/action-gh-release/pull/109/files#diff-a248ff5ec76368168c745273fee0601b243545fdca37aa3bec76ef9e9365fdb7R189
Can you open a specific issue for that so that the info doesn’t get lost in the mix?
the main issue the causing the error breaking releases is now fixed in https://github.com/softprops/action-gh-release/releases/tag/v0.1.12 (v1 tag was updated)
there may be smaller cosmetic issues but the main issue is resolved