Skip to content
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

action inlined body 3 times upon failed release #146

Open
clux opened this issue Aug 10, 2021 · 1 comment
Open

action inlined body 3 times upon failed release #146

clux opened this issue Aug 10, 2021 · 1 comment

Comments

@clux
Copy link

clux commented Aug 10, 2021

Extracted from #140 to avoid it getting lost. Thank you for all your work on this action 🙇

Came from a CI run yesterday on the 9th of August which failed like in #140 .

Run softprops/action-gh-release@v1
  with:
    body_path: release.txt
    token: ***
  env:
    GITHUB_TOKEN: ***
👩‍🏭 Creating new GitHub release for tag 0.59.0...
⚠️ GitHub release failed with status: 404
undefined
retrying... (2 retries remaining)
👩‍🏭 Creating new GitHub release for tag 0.59.0...
⚠️ GitHub release failed with status: 422
[{"resource":"Release","code":"already_exists","field":"tag_name"}]
retrying... (1 retries remaining)
👩‍🏭 Creating new GitHub release for tag 0.59.0...
⚠️ 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.

The result of this retrying seems to somehow have been that the body text got appended to the existing release, so we ended up with 3 release texts in the release. kube-rs/kube#620 has the full detail.

Note that I don't know if it's still an issue after your main fix, or if it is coupled to the the retry behaviour, just seems suspect.

@softprops
Copy link
Owner

It’s still and issue as far as I know looking into it in #145

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants