docs/content/graphql/overview/breaking-changes.md at copilot/add-changelog-file

mirror of synced 2025-12-21 10:57:10 -05:00

Files

Kevin Heis 1cd5e13652 Deprecate 3.12 (#55505 )

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
Co-authored-by: Felicity Chapman <felicitymay@github.com>
Co-authored-by: Sarah Schneider <sarahs@github.com>

2025-05-06 18:25:53 +00:00

1.1 KiB

Raw Permalink Blame History

title, intro, redirect_from, versions, topics, autogenerated

title

intro

redirect_from

versions

topics

autogenerated

Breaking changes

Learn about recent and upcoming breaking changes to the {% data variables.product.prodname_dotcom %} GraphQL API.

/v4/breaking_changes

fpt	ghec	ghes
*	*	*

API

graphql

About breaking changes

Breaking changes are any changes that might require action from our integrators. We divide these changes into two categories:

Breaking: Changes that will break existing queries to the GraphQL API. For example, removing a field would be a breaking change.
Dangerous: Changes that won't break existing queries but could affect the runtime behavior of clients. Adding an enum value is an example of a dangerous change.

We'll announce upcoming breaking changes at least three months before making changes to the GraphQL schema, to give integrators time to make the necessary adjustments. Changes go into effect on the first day of a quarter (January 1st, April 1st, July 1st, or October 1st). For example, if we announce a change on January 15th, it will be made on July 1st.

1.1 KiB Raw Permalink Blame History

About breaking changes

1.1 KiB

Raw Permalink Blame History