fix: ensure statusCode is always an integer

[Uzlopak]

I have some bug, where the status code is set to a string value. One way to fix it, is by enforcing status to be always an integer.

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[Uzlopak]

@gr2m
@wolfy1339

could you consider reviewing this please?

[wolfy1339]

This only changes it on the error. Should there not be a middleware in @octokit/request instead

[Uzlopak]

@wolfy1339

I am still investigating on the original issue. But this can be make it more resilient anyway. So I would still recommend the PR.

[gr2m]

I'm okay with it, just would use isNan

[Uzlopak]

@wolfy1339
@gr2m

Can we please merge it? THen I could check if this workaround works on gcf. :)

[github-actions]

🎉 This issue has been resolved in version 6.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀