Skip to main content
Nous publions des mises à jour fréquentes de notre documentation, et la traduction de cette page peut encore être en cours. Pour obtenir les informations les plus actuelles, consultez la documentation anglaise.
All products
GraphQL API

Changements cassants

Dans cet article

Découvrez les changements cassants récents et à venir qui concernent l’API GraphQL GitHub.

À propos des changements cassants

Les changements cassants sont tous les changements qui peuvent nécessiter une action de la part de nos intégrateurs. Nous répartissons ces changements en deux catégories :

  • Cassants : changements qui interrompent les requêtes existantes à l’API GraphQL. Par exemple, la suppression d’un champ constitue un changement cassant.
  • Dangereux : changements qui n’interrompent pas les requêtes existantes, mais qui peuvent affecter le comportement d’exécution des clients. L’ajout d’une valeur d’enum est un exemple de changement dangereux.

Nous nous efforçons de fournir des API stables pour nos intégrateurs. Lorsqu’une nouvelle fonctionnalité est toujours en cours d’évolution, nous la publions derrière une préversion de schéma.

Nous annoncerons les changements cassants à venir au moins trois mois avant de modifier le schéma GraphQL, afin de donner aux intégrateurs le temps d’apporter les ajustements nécessaires. Les changements entrent en vigueur le premier jour d’un trimestre (1er janvier, 1er avril, 1er juillet ou 1er octobre). Par exemple, si nous annonçons une modification le 15 janvier, elle sera apportée le 1er juillet.

Changes scheduled for 2022-07-01

  • Breaking A change will be made to Enterprise.userAccounts.

    Description:

    userAccounts will be removed. Use the Enterprise.members field instead.

    Reason:

    The Enterprise.userAccounts field is being removed.

  • Breaking A change will be made to AddPullRequestToMergeQueueInput.branch.

    Description:

    branch will be removed.

    Reason:

    PRs are added to the merge queue for the base branch, the branch argument is now a no-op

Changes scheduled for 2022-04-01

  • Breaking A change will be made to Repository.defaultMergeQueue.

    Description:

    defaultMergeQueue will be removed. Use Repository.mergeQueue instead.

    Reason:

    defaultMergeQueue will be removed.

Changes scheduled for 2021-10-01

  • Breaking A change will be made to ReactionGroup.users.

    Description:

    users will be removed. Use the reactors field instead.

    Reason:

    Reactors can now be mannequins, bots, and organizations.

Changes scheduled for 2021-06-21

  • Breaking A change will be made to PackageType.DOCKER.

    Description:

    DOCKER will be removed.

    Reason:

    DOCKER will be removed from this enum as this type will be migrated to only be used by the Packages REST API.

Changes scheduled for 2021-01-01

  • Breaking A change will be made to MergeStateStatus.DRAFT.

    Description:

    DRAFT will be removed. Use PullRequest.isDraft instead.

    Reason:

    DRAFT state will be removed from this enum and isDraft should be used instead

  • Breaking A change will be made to EnterpriseOutsideCollaboratorEdge.isUnlicensed.

    Description:

    isUnlicensed will be removed.

    Reason:

    All outside collaborators consume a license

  • Breaking A change will be made to EnterpriseMemberEdge.isUnlicensed.

    Description:

    isUnlicensed will be removed.

    Reason:

    All members consume a license

Changes scheduled for 2020-10-01

  • Breaking A change will be made to PullRequest.timeline.

    Description:

    timeline will be removed. Use PullRequest.timelineItems instead.

    Reason:

    timeline will be removed

  • Breaking A change will be made to Issue.timeline.

    Description:

    timeline will be removed. Use Issue.timelineItems instead.

    Reason:

    timeline will be removed

Changes scheduled for 2020-07-01

  • Breaking A change will be made to EnterprisePendingMemberInvitationEdge.isUnlicensed.

    Description:

    isUnlicensed will be removed.

    Reason:

    All pending members consume a license

Changes scheduled for 2020-01-01

  • Breaking A change will be made to UnassignedEvent.user.

    Description:

    user will be removed. Use the assignee field instead.

    Reason:

    Assignees can now be mannequins.

  • Breaking A change will be made to EnterpriseBillingInfo.seats.

    Description:

    seats will be removed. Use EnterpriseBillingInfo.totalLicenses instead.

    Reason:

    seats will be replaced with totalLicenses to provide more clarity on the value being returned

  • Breaking A change will be made to EnterpriseBillingInfo.availableSeats.

    Description:

    availableSeats will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.

    Reason:

    availableSeats will be replaced with totalAvailableLicenses to provide more clarity on the value being returned

  • Breaking A change will be made to AssignedEvent.user.

    Description:

    user will be removed. Use the assignee field instead.

    Reason:

    Assignees can now be mannequins.

Changes scheduled for 2019-04-01

  • Breaking A change will be made to LegacyMigration.uploadUrlTemplate.

    Description:

    uploadUrlTemplate will be removed. Use uploadUrl instead.

    Reason:

    uploadUrlTemplate is being removed because it is not a standard URL and adds an extra user step.