Sobre alterações significativas
Alterações significativas são quaisquer mudanças que possam exigir ação dos nossos integrantes. Dividimos essas alterações em duas categorias:
- Interruptivas: alterações que interromperão as consultas existentes na API do GraphQL. Por exemplo, a eliminação de um campo seria uma mudança decisiva.
- Perigosas: alterações que não interromperão as consultas existentes, mas que poderão afetar o comportamento de runtime dos clientes. Adicionar um valor de enumerador é um exemplo de uma alteração perigosa.
Nós nos esforçamos para fornecer APIs estáveis para os nossos integrantes. Quando um novo recurso ainda está em evolução, nós o lançamos por trás de uma versão prévia de esquema.
Vamos anunciar as próximas mudanças significativas em andamento pelo menos três meses antes de fazer alterações no esquema do GraphQL para dar tempo aos integradores de fazer os ajustes necessários. As alterações entram em vigor no primeiro dia do trimestre (1 de janeiro, 1 de abril, 1 de julho ou 1 de outubro). Por exemplo, se anunciarmos uma mudança no dia 15 de Janeiro, ela entrará em vigor no dia 1 de julho.
Changes scheduled for 2023-04-01
- Breaking A change will be made to Repository.squashPrTitleUsedAsDefault.Description:squashPrTitleUsedAsDefaultwill be removed. UseRepository.squashMergeCommitTitleinstead.Reason:squashPrTitleUsedAsDefaultwill be removed.
- Breaking A change will be made to ProjectV2View.verticalGroupBy.Description:verticalGroupBywill be removed. Check out theProjectV2View#vertical_group_by_fieldsAPI as an example for the more capable alternative.Reason:The ProjectV2View#vertical_group_byAPI is deprecated in favour of the more capableProjectV2View#vertical_group_by_fieldsAPI.
- Breaking A change will be made to ProjectV2View.sortBy.Description:sortBywill be removed. Check out theProjectV2View#sort_by_fieldsAPI as an example for the more capable alternative.Reason:The ProjectV2View#sort_byAPI is deprecated in favour of the more capableProjectV2View#sort_by_fieldsAPI.
- Breaking A change will be made to ProjectV2View.groupBy.Description:groupBywill be removed. Check out theProjectV2View#group_by_fieldsAPI as an example for the more capable alternative.Reason:The ProjectV2View#order_byAPI is deprecated in favour of the more capableProjectV2View#group_by_fieldAPI.
Changes scheduled for 2023-01-01
- Breaking A change will be made to ProjectV2View.visibleFields.Description:visibleFieldswill be removed. Check out theProjectV2View#fieldsAPI as an example for the more capable alternative.Reason:The ProjectV2View#visibleFieldsAPI is deprecated in favour of the more capableProjectV2View#fieldsAPI.
- Breaking A change will be made to ProjectNextFieldType.TRACKS.Description:TRACKSwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.TRACKED_BY.Description:TRACKED_BYwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.TITLE.Description:TITLEwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.TEXT.Description:TEXTwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.SINGLE_SELECT.Description:SINGLE_SELECTwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.REVIEWERS.Description:REVIEWERSwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.REPOSITORY.Description:REPOSITORYwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.NUMBER.Description:NUMBERwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.MILESTONE.Description:MILESTONEwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.LINKED_PULL_REQUESTS.Description:LINKED_PULL_REQUESTSwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.LABELS.Description:LABELSwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.ITERATION.Description:ITERATIONwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.DATE.Description:DATEwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to ProjectNextFieldType.ASSIGNEES.Description:ASSIGNEESwill be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.Reason:The ProjectNextAPI is deprecated in favour of the more capableProjectV2API.
- Breaking A change will be made to Commit.changedFiles.Description:changedFileswill be removed. UsechangedFilesIfAvailableinstead.Reason:changedFileswill be removed.
Changes scheduled for 2022-10-01
- Breaking A change will be made to RepositoryVulnerabilityAlert.fixReason.Description:fixReasonwill be removed.Reason:The fixReasonfield is being removed. You can still usefixedAtanddismissReason.
- Breaking A change will be made to RemovePullRequestFromMergeQueueInput.branch.Description:branchwill be removed.Reason:PRs are removed from the merge queue for the base branch, the branchargument is now a no-op
- Breaking A change will be made to DependencyGraphDependency.packageLabel.Description:packageLabelwill be removed. Use normalizedpackageNamefield instead.Reason:packageLabelwill be removed.
Changes scheduled for 2022-07-01
- Breaking A change will be made to AddPullRequestToMergeQueueInput.branch.Description:branchwill be removed.Reason:PRs are added to the merge queue for the base branch, the branchargument is now a no-op
Changes scheduled for 2021-10-01
- Breaking A change will be made to ReactionGroup.users.Description:userswill be removed. Use thereactorsfield 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:DOCKERwill 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:DRAFTwill be removed. Use PullRequest.isDraft instead.Reason:DRAFT state will be removed from this enum and isDraftshould be used instead
Changes scheduled for 2020-10-01
- 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
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 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.