fix: revert breking changes

[wolfy1339]

This reverts commit dea7233554363ae4f6ea55c739fdf321aa365c17.

Resolves #ISSUE_NUMBER

Requires #355 to be merged first

---

Before the change?

After the change?

Pull request checklist

• [ ] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• [ ] Yes
• [ ] No

---

[github-actions[bot]]

👋 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 labled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[wolfy1339]

Can you get #355 as well

[octokitbot]

:tada: This PR is included in version 18.1.1 :tada:

The release is available on:

• GitHub release
• npm package (@release-18.x dist-tag)
• npm package (@release-18.x dist-tag)
• npm package (@release-18.x dist-tag)
• npm package (@release-18.x dist-tag)
• npm package (@release-18.x dist-tag)
• npm package (@release-18.x dist-tag)
• npm package (@release-18.x dist-tag)

Your semantic-release bot :package::rocket: