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
Handle incorrect return type from Octokit paginate plugin #12791
Conversation
Signed-off-by: Eric Voshall <6836155+ericvoshall@users.noreply.github.com>
Signed-off-by: Eric Voshall <6836155+ericvoshall@users.noreply.github.com>
Changed Packages
|
Is this something to do with the code requiring a later version of octokit than what you have installed or are the types outdated? It would be interesting to know a little more what's going on here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's get this in for now, as I want to get this fixed and shipped for tomorrow at least.
Thanks for this! 🙏 |
Thanks for the merge!
It's an issue with the types - there's an issue open in the project here for the same thing. |
@benjdlambert do you plan to release a hotfix for this change or should we use the next version? Our catalog scanning is failing because it can not handle the repositories. |
1.5 is planned for next week, so we will release it then. If you need it sooner then feel free to jump on the |
Hi, any chance this could be released as a patch in the 1.4 series while we wait for 1.5 as it's causing issues in the latest stable release? |
@mwz I didn't try it but you can force via yarn to use an older version of octokit. "resolutions": {
`"@octokit/rest": "^18.12.0"`
} |
We used |
Hey, I just made a Pull Request!
Handle an issue with an incorrect return type from the Octokit paginate plugin. This fixes #12761.
✔️ Checklist
Signed-off-by
line in the message. (more info)