ST-2026-266 · API & schema lifecycle
GitHub makes the asynchronous merge API generally available
GitHub's asynchronous merge API is generally available for REST and GraphQL clients, and stacked pull requests are supported only through the asynchronous path.
GitHubmerge APIRESTGraphQLstacked pull requests
Previous state
API clients commonly used synchronous merge operations and stacked pull requests lacked this supported asynchronous path.
Current state
REST and GraphQL clients can use asynchronous merges; GitHub identifies the asynchronous path as the supported route for stacked pull requests.
Affected users
Who needs to care
Developers and tools automating GitHub pull request merges.
Required response
What to do
Adopt the asynchronous merge operation where completion is not immediate, and use it for stacked pull-request workflows.
Evidence boundary
What the source does not prove
This records the official API capability and stacked-PR boundary; it does not claim synchronous merge endpoints are retired.
Lifecycle history
Dated event sequence
- General availability
GitHub announced general availability of the asynchronous merge API.
Evidence ledger
First-party sources
- 01GitHub Changelog — GitHub async merge API generally available
Official GitHub API capability authority · 2026-10-01
Open official source ↗