-
Notifications
You must be signed in to change notification settings - Fork 119
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
Exceeding a secondary rate limit even with 10.0.7 #867
Comments
Hmm it's a bummer that the "secondary rate limits" can be have many causes, it's what was previously referred to as abuse limit. We won't be able to 100% avoid them, but there are more things we can do to prevent them. But first thing of business is to make sure we log out the full error object |
Hey, actually I removed part of the error as I thought it wasn't meaningful, but I guess I was wrong heh. The Here is the full error log with the 2 objects:
|
Great, thanks @victor-keltio But, this does look like it's still making a request to the Github Issue Search Rest API 🤔 What'd you think @gr2m!? |
This request is sent to check if an open issue created by semantic-release exists. Either to close it if the releases succeeded or to avoid creating duplicated issues if one already exists. But it's only one request, it's interesting that this one got rate limited. Can you tell me the |
Hey there, I saw that a recent release was made to use GraphQL instead of Github's API to avoid hitting the rate limits.
I bumped my
@semantic-release/github
version to use^10.0.7
but even with this, I'm hitting the limits:Is there anything I can do to fix this? I've tried releasing a new version after having waited 10min, but I faced the same issue.
Many thanks for your work and your help :)
The text was updated successfully, but these errors were encountered: