For repos with a lot of commits/pull-requests, the release process fails with:
✖ error Went over abuse rate limit GET /repos/{owner}/{repo}/releases/latest, retrying in 1m.
✖ error Went over abuse rate limit GET /repos/{owner}/{repo}/issues/{issue_number}, retrying in 1m.
✖ error Went over abuse rate limit GET /repos/{owner}/{repo}/issues/{issue_number}, retrying in 1m.
✖ error Went over abuse rate limit GET /repos/{owner}/{repo}/issues/{issue_number}, retrying in 1m.
Expected behavior
Release process should not break.
Environment information:
Additional context
This seems to be a secondary rate limit error. I don't see any prior log messages like Request quota exhausted....
octokit/plugin-throttling has a fallbackSecondaryRateRetryAfter configuration option. Perhaps that could be exposed also in the auto configuration so that I could increase it?
Alternatively we could upgrade @octokit/plugin-throttling to >=v5.2.3, because the rate limit was increased from 5 to 60.
Update: The upgrade seems to be the way to go, because not only was the rate limit increased, also the implementation was improved.
For repos with a lot of commits/pull-requests, the release process fails with:
Expected behavior
Release process should not break.
Environment information:
Additional context
This seems to be a secondary rate limit error. I don't see any prior log messages like
Request quota exhausted....octokit/plugin-throttling has a
fallbackSecondaryRateRetryAfterconfiguration option. Perhaps that could be exposed also in theautoconfiguration so that I could increase it?Alternatively we could upgrade
@octokit/plugin-throttlingto>=v5.2.3, because the rate limit was increased from 5 to 60.Update: The upgrade seems to be the way to go, because not only was the rate limit increased, also the implementation was improved.