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
When I push a new tag, it starts to run the workflow, but it gives an error
👩🏭 Creating new GitHub release for tag v2.0.3...
⚠️ GitHub release failed with status: 404
undefined
retrying... (2 retries remaining)
👩🏭 Creating new GitHub release for tag v2.0.3...
⚠️ GitHub release failed with status: 4[22](https://github.com/xp-work/Test2/actions/runs/5655268949/job/15320028840#step:8:23)
[{"resource":"Release","code":"already_exists","field":"tag_name"}]
retrying... (1 retries remaining)
👩🏭 Creating new GitHub release for tag v2.0.3...
⚠️ GitHub release failed with status: 422
[{"resource":"Release","code":"already_exists","field":"tag_name"}]
retrying... (0 retries remaining)
❌ Too many retries. Aborting...
Error: Too many retries.
When I went to check Release, I found a new release, indicating that the release was successful, but an error was reported in the workflow
Please tell me how to handle de-posting from an already existing tag without getting an error?
Or whether it should be added to the publishing process to determine whether the tag exists before deciding on the following actions
The text was updated successfully, but these errors were encountered:
@AlbertXiaoPeng not sure if you find the problem. If not, can you check if you have the Discussions enabled in your repository and that the discussion_category_name name you use (Release in your example) is a valid category?
As mentioned in #110 (comment), the 404 when creating a release seems to be coming from the an invalid discussion category.
My workflow.yml
When I push a new tag, it starts to run the workflow, but it gives an error
When I went to check Release, I found a new release, indicating that the release was successful, but an error was reported in the workflow
Please tell me how to handle de-posting from an already existing tag without getting an error?
Or whether it should be added to the publishing process to determine whether the tag exists before deciding on the following actions
The text was updated successfully, but these errors were encountered: