← All provider guides

GitHub API breaking changes (2025–2026): complete tracker and fixes

github 10 breaking / deprecation entries 2025–2026

GitHub ships API and SDK changes continuously. Most are additive — but the ones that are not can silently break integrations that worked yesterday. This page is the complete, continuously regenerated record of every GitHub breaking change and deprecation in the mendapi change database: 10 entries (9 breaking, 1 deprecation), each linked to its upstream source and, where possible, to a concrete fix.

How to read this page

Every entry carries a fixability verdict from the mendapi adjudication pipeline: code-fixable means a mechanical code change repairs the break (0 entries); not code-fixable means the change requires a business decision, credential provisioning, or upstream action that no codemod can produce (9 entries). Entries marked auto-fix pack have a deterministic, gold-tested migration pack that mendapi fix can apply locally.

Am I affected?

Reading a changelog tells you what changed — not whether your code uses the affected surface. The mendapi scanner answers that locally, in about 30 seconds, without any code leaving your machine:

npx mendapi sync
# -> one network call: pulls the change feed into a local database
npx mendapi scan
# -> N findings: file, line, provider, confidence
mendapi deps --match
# -> which of the changes below actually hit your endpoints

See Getting Started for the full workflow and the security model for why zero code upload is the default and only mode.

Complete GitHub breaking change timeline

Automated migration packs for GitHub

No deterministic pack ships for GitHub yet; code-fixable entries above carry reviewed migration guidance, and BYO-LLM draft fixes can generate patch drafts on your own compute.

Recent GitHub releases adjudicated non-breaking

Not paging you is the other half of the job. The same pipeline that produced the timeline above also cleared 25 GitHub changes as additive or fix-only — releases an integrator can upgrade through without a migration. The most recent:

Measured: when every verdict in the feed says no codemod

The GitHub entries above come from changelog capture, not a spec-diff corridor — so unlike the Stripe or Twilio trackers this page makes no corridor claim. What every entry does carry is an adjudicated fixability verdict with a machine-readable reason, and GitHub is the extreme case: of the 10 breaking and deprecation entries above, 0 are code-fixable, 9 are not and 1 is unclear (documented too thinly to rule a codemod in or out, so it stays in the coverage denominator). Not one carries a codemod today — they are product retirements, platform policy changes and spec transitions the vendor absorbs. An unadjudicated feed would page you 10 times; the verdicts tell you, with reasons, that the work is triage and planning, not patching.

A verdict that says the vendor absorbed it. “GitHub MCP Server supports the next MCP specification” sounds like a wire-protocol break. The adjudicated reason reads: Changelog post fetched in full: MCP stateless transition is absorbed by backwards-compatible tier 1 SDKs; GitHub states consumers need do nothing to maintain support. No breaking wire surface for SDK-based consumers, so no fix exists or is needed - honest exit from the denominator. A headline that implies migration work, and a verdict that measures none — that is exactly the noise adjudication exists to filter.

A verdict that says this is a business decision. “GitHub Models is now retired” is a genuine break — the inference API is gone — but the reason is honest about what a tool can do: GitHub Models product retirement (playground, model catalog, inference API, BYOK all withdrawn with no successor endpoint); choosing a replacement inference provider is a business decision, not a mechanical mend. Pretending a codemod could pick your replacement provider would be lying; flagging the retirement early, with its scope, is the honest maximum.

Monitoring GitHub going forward

This page is regenerated from the change database, which is fed by release feeds, changelog capture and OpenAPI spec diffing — so it does not depend on GitHub writing a perfect changelog. mendapi monitors 84125 change records across 20 providers; hosted plans watch your repos continuously and open fix PRs when a change lands. See pricing.

Frequently asked questions

Related

• API breaking change detection — how upstream breakage is caught before it ships, and why default severity gates stay silent.
• All breaking-change reports — per-change deep dives with migration guides.
• All monitored providers — live change counts.
• Migration pack catalog — every deterministic fix mendapi ships.