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

github release automation triple-inlined changes #620

Closed
clux opened this issue Aug 9, 2021 · 1 comment
Closed

github release automation triple-inlined changes #620

clux opened this issue Aug 9, 2021 · 1 comment

Comments

@clux
Copy link
Member

clux commented Aug 9, 2021

In 0.59.0. Not sure why. I edited it away, but people watching would have gotten the confusing the email:

Screenshot from 2021-08-09 20-30-50

The process uses effectively:

./scripts/release-gh.sh 2021-08-09
cat release.txt

through the release action.

It seems the github action failed, even though the release made it: https://github.com/kube-rs/kube-rs/runs/3283932565?check_suite_focus=true , strange error:

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.

Going to put this down as some transient strangeness (even though the action has seen some updates recently). Noting this for future clux releasing 0.60.0.

@clux
Copy link
Member Author

clux commented Sep 2, 2021

Did not see this with our latest release, but that's probably because the action retrying didn't happen. Anyway, closing this because it didn't affect us, but leaving the upstream bug.

@clux clux closed this as completed Sep 2, 2021
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

1 participant