https://docs.github.com/en/rest/about-the-rest-api/api-versions?apiVersion=2026-03-10#specifying-an-api-version
If you specify an API version that is no longer supported, you will receive a 410 Gone response.
There's stuff that talks about a HTTP 410 response, but I don't know how to trigger that.
There are currently two api versions:
It'd be really nice if you introduced another api version:
(It could be 2008-01-01, 2008-02-01, 2008-02-07, or 2008-04-09, but 04-01 seems nicest)
And have it return HTTP 410 for any api calls. That'd make it easy for people to imagine calling an endpoint and getting an HTTP 410 back from github based on a versioned api expiring. It'd mean that both GitHub and consumers of GitHub could test this codepath instead of relying on hallucinations.
https://docs.github.com/en/rest/about-the-rest-api/api-versions?apiVersion=2026-03-10#specifying-an-api-version
There's stuff that talks about a
HTTP 410response, but I don't know how to trigger that.There are currently two api versions:
It'd be really nice if you introduced another api version:
(It could be 2008-01-01, 2008-02-01, 2008-02-07, or 2008-04-09, but 04-01 seems nicest)
And have it return
HTTP 410for any api calls. That'd make it easy for people to imagine calling an endpoint and getting anHTTP 410back from github based on a versioned api expiring. It'd mean that both GitHub and consumers of GitHub could test this codepath instead of relying on hallucinations.