[BREAKING CHANGES]: int to long Ids for PreReceiveHook, Deployment Environments, Repository, Org Team, Repo Invitations, Public Key, Project Cards, Organization Invitation, Migrations, GpgKey, Deployment, Authorizations, Accounts / Profiles, Codespace / Workspaces

[nickfloyd]

Relates to #2893

We have uncovered a series of issues around the IDs used across our API surface (Issues, Pull Requests, deployments, etc.. are all effected).

The GitHub database schemas were changed to accommodate for the growing IDs - migrating many of them from int to bigint - this SDK was lagging behind in those changes so when API calls began to return data that was too large for the types defined in our SDKs - their apps, integration, and automation began to break.

---

Before the change?

• Overflow issues would happen when calling an API that returned a long (e.g. a release ID) but the class had this defined as an int - this would cause the SDK to throw an overflow exception.

After the change?

• We have updated the int types to be long across the SDKs - this will allow for the larger IDs to be returned without causing an overflow exception.

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

---

[kfcampbell]

Awesome job! This is super helpful for our users.