Runner deprecations: registration_deprecates_at is declared on the response but never returned
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- openapi
- Domain
- api, documentation
Research direction
Locate the OpenAPI 200-response schemas for actions/get-runner-version-deprecation-for-repo and actions/get-runner-version-deprecation-for-org. Compare the registration_deprecates_at schema and description with the observed responses and sibling runtime_deprecates_at field. Done means the specification either documents the field's unpopulated status or reflects a populated response accurately.
Written by the indexing model from the issue text.
Description
Description
The runner version end-of-life operations actions/get-runner-version-deprecation-for-repo
and actions/get-runner-version-deprecation-for-org declare registration_deprecates_at
on their 200 schema, a nullable date-time, "The date after which this runner version
can no longer register".
I have not been able to get it returned. Every version between 2.321.0 and 2.337.0
comes back with runner_version and runtime_deprecates_at only:
2.325.0 {"runner_version":"2.325.0","runtime_deprecates_at":"2025-09-11T13:58:34Z"}
2.328.0 {"runner_version":"2.328.0","runtime_deprecates_at":"2025-12-16T17:40:26Z"}
2.335.1 {"runner_version":"2.335.1","runtime_deprecates_at":"2026-09-24T15:30:55Z"}
2.337.0 {"runner_version":"2.337.0","runtime_deprecates_at":null}
2.325.0 and 2.328.0 are below the 2.329.0 floor that
the enforcement timeline
says "won't be able to register or reregister", so if any version has a registration
date it should be those. It is not an omit-when-null rule either, since 2.337.0
keeps the sibling key as an explicit null.
Only runner_version is required, so omitting it is legal against the description.
That is what makes it a client problem rather than a validation error: codegen yields
an optional nullable field that reads the same whether nothing populates it or this
version genuinely has no registration deadline, and those want opposite handling.
Expected
Either registration_deprecates_at is populated, or its description says it is not
currently populated, so clients know the absence is not a signal.
- Dominant language
- No language data
- Stars
- 1.6k
- Forks
- 342
- Avg merge
- 3h 33m
- Merged PRs (30d)
- 51
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 82/100
github/rest-api-description#7201 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/rest-api-description#7163 ·
-
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 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7096 ·
All issues in github/rest-api-description
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
punkpeye/mcp-remote#369 ·
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·
-
bug p:3-mid pydanty:bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
pydantic/pydantic-ai#8643 · 1 comment ·