Критические изменения

Сведения о критических изменениях

Критические изменения — это любые изменения, которые могут потребовать действий от интеграторов. Эти изменения делятся на две категории:

Критические. Изменения, которые прерывают выполнение текущих запросов к API GraphQL. Например, критическим изменением является удаление поля.
Опасные. Изменения, которые не прерывают выполнение существующих запросов, но могут повлиять на поведение среды выполнения клиентов. Опасным изменением является, например, добавление значения в перечисление.

Мы стремимся предоставлять стабильные API для наших интеграторов. Когда работа над новой функцией еще идет, мы выпускаем ее в рамках предварительной версии схемы.

Мы объявляем о предстоящих критических изменениях минимум за три месяца до их внедрения в схему GraphQL, чтобы дать интеграторам время для внесения необходимых корректировок. Изменения вступают в силу в первый день квартала (1 января, 1 апреля, 1 июля или 1 октября). Например, если об изменении объявлено 15 января, оно будет внедрено 1 июля.

Changes scheduled for 2023-04-01

Breaking A change will be made to Repository.squashPrTitleUsedAsDefault.
Description:
squashPrTitleUsedAsDefault will be removed. Use Repository.squashMergeCommitTitle instead.
Reason:
squashPrTitleUsedAsDefault will be removed.

Breaking A change will be made to ProjectV2View.verticalGroupBy.
Description:
verticalGroupBy will be removed. Check out the ProjectV2View#vertical_group_by_fields API as an example for the more capable alternative.
Reason:
The ProjectV2View#vertical_group_by API is deprecated in favour of the more capable ProjectV2View#vertical_group_by_fields API.

Breaking A change will be made to ProjectV2View.sortBy.
Description:
sortBy will be removed. Check out the ProjectV2View#sort_by_fields API as an example for the more capable alternative.
Reason:
The ProjectV2View#sort_by API is deprecated in favour of the more capable ProjectV2View#sort_by_fields API.

Breaking A change will be made to ProjectV2View.groupBy.
Description:
groupBy will be removed. Check out the ProjectV2View#group_by_fields API as an example for the more capable alternative.
Reason:
The ProjectV2View#order_by API is deprecated in favour of the more capable ProjectV2View#group_by_field API.

Changes scheduled for 2023-01-01

Breaking A change will be made to ProjectV2View.visibleFields.
Description:
visibleFields will be removed. Check out the ProjectV2View#fields API as an example for the more capable alternative.
Reason:
The ProjectV2View#visibleFields API is deprecated in favour of the more capable ProjectV2View#fields API.

Breaking A change will be made to ProjectNextFieldType.TRACKS.
Description:
TRACKS will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.TRACKED_BY.
Description:
TRACKED_BY will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.TITLE.
Description:
TITLE will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.TEXT.
Description:
TEXT will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.SINGLE_SELECT.
Description:
SINGLE_SELECT will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.REVIEWERS.
Description:
REVIEWERS will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.REPOSITORY.
Description:
REPOSITORY will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.NUMBER.
Description:
NUMBER will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.MILESTONE.
Description:
MILESTONE will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.LINKED_PULL_REQUESTS.
Description:
LINKED_PULL_REQUESTS will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.LABELS.
Description:
LABELS will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.ITERATION.
Description:
ITERATION will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.DATE.
Description:
DATE will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to ProjectNextFieldType.ASSIGNEES.
Description:
ASSIGNEES will 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 ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

Breaking A change will be made to Commit.changedFiles.
Description:
changedFiles will be removed. Use changedFilesIfAvailable instead.
Reason:
changedFiles will be removed.

Changes scheduled for 2022-10-01

Breaking A change will be made to RepositoryVulnerabilityAlert.fixReason.
Description:
fixReason will be removed.
Reason:
The fixReason field is being removed. You can still use fixedAt and dismissReason.

Breaking A change will be made to RemovePullRequestFromMergeQueueInput.branch.
Description:
branch will be removed.
Reason:
PRs are removed from the merge queue for the base branch, the branch argument is now a no-op

Breaking A change will be made to DependencyGraphDependency.packageLabel.
Description:
packageLabel will be removed. Use normalized packageName field instead.
Reason:
packageLabel will be removed.

Changes scheduled for 2022-07-01

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 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

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-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 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.

Критические изменения

В этой статье