About breaking changes
Breaking changes are any changes that might require action from our integrators. We divide these changes into two categories:
- Breaking: Changes that will break existing queries to the GraphQL API. For example, removing a field would be a breaking change.
- Dangerous: Changes that won't break existing queries but could affect the runtime behavior of clients. Adding an enum value is an example of a dangerous change.
We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a schema preview.
We'll announce upcoming breaking changes at least three months before making changes to the GraphQL schema, to give integrators time to make the necessary adjustments. Changes go into effect on the first day of a quarter (January 1st, April 1st, July 1st, or October 1st). For example, if we announce a change on January 15th, it will be made on July 1st.
Changes scheduled for 2021-01-01
- Breaking A change will be made to
MergeStateStatus.DRAFT.Description:
DRAFTwill be removed. Use PullRequest.isDraft instead.Reason:
DRAFT state will be removed from this enum and
isDraftshould be used instead
- Breaking A change will be made to
EnterprisePendingCollaboratorEdge.isUnlicensed.Description:
isUnlicensedwill be removed.Reason:
All pending collaborators consume a license
- Breaking A change will be made to
EnterpriseOutsideCollaboratorEdge.isUnlicensed.Description:
isUnlicensedwill be removed.Reason:
All outside collaborators consume a license
- Breaking A change will be made to
EnterpriseMemberEdge.isUnlicensed.Description:
isUnlicensedwill be removed.Reason:
All members consume a license
Changes scheduled for 2020-10-01
- Breaking A change will be made to
Sponsorship.sponsor.Description:
sponsorwill be removed. UseSponsorship.sponsorEntityinstead.Reason:
Sponsorship.sponsorwill be removed.
- Breaking A change will be made to
RepositoryInvitationOrderField.INVITEE_LOGIN.Description:
INVITEE_LOGINwill be removed.Reason:
INVITEE_LOGINis no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.
- Breaking A change will be made to
PullRequest.timeline.Description:
timelinewill be removed. Use PullRequest.timelineItems instead.Reason:
timelinewill be removed
- Breaking A change will be made to
Issue.timeline.Description:
timelinewill be removed. Use Issue.timelineItems instead.Reason:
timelinewill be removed
- Breaking A change will be made to
EnterpriseOwnerInfo.pendingCollaborators.Description:
pendingCollaboratorswill be removed. Use thependingCollaboratorInvitationsfield instead.Reason:
Repository invitations can now be associated with an email, not only an invitee.
Changes scheduled for 2020-07-01
- Breaking A change will be made to
EnterprisePendingMemberInvitationEdge.isUnlicensed.Description:
isUnlicensedwill be removed.Reason:
All pending members consume a license
Changes scheduled for 2020-04-01
- Breaking A change will be made to
Sponsorship.maintainer.Description:
maintainerwill be removed. UseSponsorship.sponsorableinstead.Reason:
Sponsorship.maintainerwill be removed.
Changes scheduled for 2020-01-01
- Breaking A change will be made to
UnassignedEvent.user.Description:
userwill be removed. Use theassigneefield instead.Reason:
Assignees can now be mannequins.
- Breaking A change will be made to
EnterpriseBillingInfo.seats.Description:
seatswill be removed. Use EnterpriseBillingInfo.totalLicenses instead.Reason:
seatswill be replaced withtotalLicensesto provide more clarity on the value being returned
- Breaking A change will be made to
EnterpriseBillingInfo.availableSeats.Description:
availableSeatswill be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.Reason:
availableSeatswill be replaced withtotalAvailableLicensesto provide more clarity on the value being returned
- Breaking A change will be made to
AssignedEvent.user.Description:
userwill be removed. Use theassigneefield instead.Reason:
Assignees can now be mannequins.
Changes scheduled for 2019-04-01
- Breaking A change will be made to
LegacyMigration.uploadUrlTemplate.Description:
uploadUrlTemplatewill be removed. UseuploadUrlinstead.Reason:
uploadUrlTemplateis being removed because it is not a standard URL and adds an extra user step.