Runner deprecations: enterprise scope is in the changelog and the 404 handler but not in the description
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- openapi
- Domain
- api, documentation
Research direction
Start in descriptions/api.github.com/api.github.com.json by comparing the existing organization and repository runner deprecation paths with the enterprise route described in the 2026-09-03 changelog. Check the corresponding documentation heading and route-specific error link; done means the description and changelog/docs consistently represent the supported scopes, with the enterprise link resolving correctly if that scope is retained.
Written by the indexing model from the issue text.
Description
Description
The 2026-09-03 changelog
says the runner version end-of-life endpoint is callable "at the repository,
organization, or enterprise level". descriptions/api.github.com/api.github.com.json
at 1.1.4 has the /orgs/{org}/ and /repos/{owner}/{repo}/ deprecations paths and no
/enterprises/{enterprise}/actions/runners* path of any kind.
A missing path alias would normally be the README's "only the most common path is
described". This looks different, because the operation name exists outside the
description and resolves to nothing. The enterprise route 404s with a route-specific
documentation_url, where an unrouted sibling gets the generic one:
$ curl -s -H "Authorization: Bearer $TOKEN" \
https://api.github.com/enterprises/SLUG/actions/runners/deprecations/2.335.1
{"message":"Not Found","documentation_url":"https://docs.github.com/rest/actions/self-hosted-runners#get-runner-version-end-of-life-schedule-for-an-enterprise","status":"404"}
$ curl -s -H "Authorization: Bearer $TOKEN" \
https://api.github.com/repos/OWNER/REPO/actions/runners/nonsense-route/2.335.1
{"message":"Not Found","documentation_url":"https://docs.github.com/rest","status":"404"}
That anchor does not exist. The docs page has the organization and repository
headings and no enterprise one, so the link lands at the top of the page. So
get-runner-version-end-of-life-schedule-for-an-enterprise is known to the error
handler and absent from both the description and the page it points at. Clients
generating from the description cannot reach enterprise scope, and clients following
the changelog have nothing to call.
Expected
Either the enterprise paths are added to the api.github.com description, or the
2026-09-03 changelog is corrected to say repository and organization only.
- Dominant language
- No language data
- Stars
- 1.6k
- Forks
- 342
- Avg merge
- 2h 23m
- Merged PRs (30d)
- 57
Contributor 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.
More from github/rest-api-description
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
github/rest-api-description#7220 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/rest-api-description#7201 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7162 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7135 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
github/rest-api-description#7111 · 1 comment ·
All issues in github/rest-api-description
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
speaches-ai/speaches#678 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Openbug ecr
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100