GitHub API Breaking Changes
On 22 June, Dev.to reported that GitHub GraphQL would drop Team.viewerSubscription and 17 audit-log entries on 1 July. The report’s sharper warning concerned partial errors: integrations could keep running while returning incomplete results. The failure could appear harmless until somebody trusts the results.
On 3 September, Dev.to reported that GitHub had quietly removed merge_commit_sha from its API. The alleged failure mode was again silent: automation could produce the wrong result without throwing an error. Related Dev.to coverage has focused on detecting breaking OpenAPI changes before production and designing around GitHub Actions cron jobs that fire less often than declared. Software remains admirably obedient when its assumptions have expired.
Taking this as factual, impact is 0%. The affected users are developers whose GraphQL queries depend on Team.viewerSubscription or the 17 audit-log entries, and teams whose automation expects merge_commit_sha. Their workflows may continue without obvious errors while consuming partial or incorrect data.
Watch GitHub’s API documentation and change records for confirmation of the removals and any migration guidance. Reproducible tests showing how existing queries and automation now behave would clarify the practical scope.
<p>An API can stay online, return 200s, and still break every client that depends on it.</p> <p>That is the uncomfortable part of API compatibility: the dangerous change often
<p>If you use GitHub's merge queue and had a rough week around April 23rd, 2026, you were not imagining things. Your code actually disappeared. Not because of a bad commit, not
<p>In the fast-paced world of modern software development, continuous integration and continuous delivery (CI/CD) pipelines are the backbone of efficient workflows. GitHub
<p>The receipt landed in my GitHub inbox on a Monday morning. </p> <p>Subject: important changes to your Copilot plan. </p> <p>Body: starting June 1, every Copilot subscription
<p>trpc has a scheduled workflow called "Lock Issues & PRs." Its own <a href="https://gitspider.com/scan/trpc/trpc?ref=devto" rel="noopener noreferrer">scorecard</a> shows it
<p>The thread connecting this week's stories is the gap between what software assumes and what hardware or bad actors actually do. From ad networks repurposed for surveillance to
<p>Breaking API contracts silently slipping into production is a pain point almost every engineering team hits eventually. A backend PR renames a field, drops a property, or
NewsHive monitors these sources continuously. All signal titles above link to the original reporting.
Intelligence by NewsHive. Need help navigating what this means for your business? Contact GeekyBee →