`HTTP 410` version promise is untestable

Open

#7,054 opened on Aug 21, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 25/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Active
Tech stack: openapi
Domain: api

Research direction

Start with the linked API versioning documentation and compare the listed versions, 2022-11-28 and 2026-03-10, with the requested 2008-04-01 version. Determine whether this repository can represent a version that returns HTTP 410 for API calls; done would make that expired-version response testable for GitHub and its consumers.

Written by the indexing model from the issue text.

Description

feature

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:

2022-11-28
2026-03-10

It'd be really nice if you introduced another api version:

2008-04-01

(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.

Dominant language: No language data
Stars: 1.6k
Forks: 342
Avg merge: 3h 33m
Merged PRs (30d): 51

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug]: Matrix progress drafts fail with "Matrix runtime not initialized" during tool activity Open

bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

openclaw/openclaw#155298 · 2 comments · 1 reaction · Opened Sep 22, 2026
[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
MCP client has no httpx timeout, so the event stream fails after 5 seconds Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Azure/azure-functions-agents-runtime#228 · Opened Sep 21, 2026
feat(mcp): friendlier error when `run_cloud_sync` is called on a disabled connection Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

airbytehq/PyAirbyte#1205 · Opened Sep 21, 2026

More Backend & API Design issues