2025-Q1
Breaking Changes2
Team.members
The `members` field on the `Team` type has been removed as it was deprecated in previous versions. This change affects queries that directly access this field. Ensure your queries use the `members.edges` or `members.nodes` pattern instead.
query { team(slug: "my-team") { members(first: 10) { nodes { login } } } }query { team(slug: "my-team") { members(first: 10) { nodes { login } } } }Update queries to use `members.edges` or `members.nodes` instead of directly accessing `members`.
Organization.billingPlan
The `billingPlan` field on the `Organization` type has been renamed to `billingInfo`. This is a breaking change for clients that query the organization's billing plan. Consumers must update their queries to use the new field name.
query { organization(login: "my-org") { billingPlan { seats } } }query { organization(login: "my-org") { billingInfo { seats } } }Rename `billingPlan` to `billingInfo` in organization queries.
Migration Checklist
Full interactive checklist →- 1Review GraphQL queries for usage of `Team.members`.
- 2Update queries to use `members.edges` or `members.nodes` where `Team.members` was used.
- 3Identify and update any queries referencing `Organization.billingPlan`.
- 4Replace `Organization.billingPlan` with `Organization.billingInfo` in relevant queries.
- 5Test all affected GraphQL endpoints to ensure they return expected data.
- 6Deploy updated code with new GraphQL query patterns.
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