GITHUB_TOKEN is invalidated after time window causing action to fail
See original GitHub issueOn Windows runners this fails with:
Run softprops/action-gh-release@v1
with:
files: livesplit-core-*.*
env:
GITHUB_TOKEN: ***
⚠️ Unexpected error fetching GitHub release for tag refs/tags/v-testing: HttpError: Bad credentials
##[error]Bad credentials
##[error]Node run failed with exit code 1
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:16 (9 by maintainers)
Top Results From Across the Web
Token expiration and revocation - GitHub Docs
If a valid OAuth token, GitHub App token, or personal access token is pushed to a public repository or public gist, the token...
Read more >Token not working, always causing 403 · Issue #11217 - GitHub
GitHub action Upload Python Package authentication fails with the token I generates for it (403). To Reproduce. Create a repo with some python ......
Read more >Logintoken are Invalidated 21.0.1 · Issue #26502 · nextcloud ...
Login via previously created token is no longer possible. All connected apps show an error message. This error exists even for older tokens...
Read more >Security hardening for GitHub Actions
Rotate secrets periodically to reduce the window of time during which a compromised secret is valid. Consider requiring review for access to secrets....
Read more >Various issues with refresh token rotation #2071 - GitHub
It means that it can throw 401 and you can handle the error on the frontend perhaps trying to signin the user or...
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 didn’t have much time to test it yet. But from the few runs I’ve done since then, I didn’t have any network errors yet. So this may indeed be resolved 😃
No, only on Windows. I’ve reordered the Windows runners to run earlier now, and so far it’s working.