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
Exhaust your unauthenticated GitHub API keys. One way to do this is to :
foriin$(seq 0 60);do
curl -fsSL https://api.github.com/repos/oven-sh/bun/releases/latest
done# Don't abuse this, for good
Don't worry this will automatically reset in 1 hour as mentioned here.
Run bun --upgrade from your terminal
This issue arrives even if you're on the latest version of terminal
What is the expected behavior?
The error could be more descriptive, instead of just HTTPForbidden possibly, as switching networks and/or waiting for just 1 hr can still solve the issue as mentioned later also.
What do you see instead?
Bun upgrade failed with error: HTTPForbidden
Please upgrade manually:
curl -fsSL https://bun.sh/install | bash
Additional information
Possible resolutions could include :
Recommend user to change to alternate network provider/VPN as rate limit are imposed per IP.
Recommend user to use GitHub Token. (Looking through the code, I believe it is supported, but I am not sure regarding this)
Recommend user to wait for 1 hour till Rate limit resets.
Don't do anything! (Current message still does sort of works in those situations, so it depends)
The text was updated successfully, but these errors were encountered:
What version of Bun is running?
1.0.29+a146856d1
What platform is your computer?
Linux 6.7.5-arch1-1 x86_64 unknown
What steps can reproduce the bug?
Exhaust your unauthenticated GitHub API keys. One way to do this is to :
Don't worry this will automatically reset in 1 hour as mentioned here.
Run
bun --upgrade
from your terminalThis issue arrives even if you're on the latest version of terminal
What is the expected behavior?
The error could be more descriptive, instead of just
HTTPForbidden
possibly, as switching networks and/or waiting for just 1 hr can still solve the issue as mentioned later also.What do you see instead?
Additional information
Possible resolutions could include :
The text was updated successfully, but these errors were encountered: