2024-Q4
Released 2024-10-01Active
Migration Effort
Low
Estimated Hours
~8h
Primary risk if skipped: API request failures or incorrect data due to using removed fields or incorrect filter arguments.
Breaking Changes2
fieldHighGitHub Enterprise CloudGitHub Enterprise ServerGitHub.com
ProjectV2.items
The `items` field on the `ProjectV2` type, previously deprecated, has been removed. This change affects queries that directly accessed `ProjectV2.items`.
Before
query { viewer { projectsV2(first: 1) { nodes { id items(first: 10) { nodes { fieldValues(first: 10) { nodes { value } } } } } } } }After
query { viewer { projectsV2(first: 1) { nodes { id itemCount } } } }→
Update queries to use the `itemCount` field or migrate to the `ProjectV2.itemAnswers` connection for accessing project items.
fieldMediumGitHub Enterprise CloudGitHub Enterprise ServerGitHub.com
Repository.pullRequests.states and Repository.issues.states
The filter arguments `states` on `Repository.pullRequests` and `Repository.issues` have been renamed to `states` to align with other similar connections. This change impacts any query filtering by PR or issue states.
Before
query { repository(name: "my-repo") { pullRequests(first: 10, states: OPEN) { nodes { title } } issues(first: 10, states: OPEN) { nodes { title } } } }After
query { repository(name: "my-repo") { pullRequests(first: 10, states: OPEN) { nodes { title } } issues(first: 10, states: OPEN) { nodes { title } } } }→
Rename the `states` argument to `states` in queries filtering `Repository.pullRequests` and `Repository.issues`.
Never get blindsided by an API change again
Deprecatr AI monitors 150+ providers, maps changes to your codebase, and delivers migration checklists before your team hits a breaking change.
Join the Waitlist