Versioned API schema
GitHub REST API create a team permission parameter removed API version POST /orgs/{org}/teams validation error
POST /orgs/{org}/teams returns validation error only on the new API version.
Agent Quick Fix
Repair against the current GitHub REST API contract, then keep the change narrow and source-backed.
Product: GitHub REST API
Current-contract area: Create-team request still sends removed permission property
Likely root cause: POST /orgs/{org}/teams returns validation error only on the new API version.
Repair direction: Verifier exercises the changed field/status/enum plus an unaffected endpoint to prevent a brittle one-off patch. Exercise strict and permissive parsing plus one downstream behavior tied to the changed field.Symptom
POST /orgs/{org}/teams returns validation error only on the new API version.
Why This Happens
Several historical response shapes are locally plausible; only the selected current API version determines fields, enums, media types, and status codes.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
GitHub REST API create a team permission parameter removed API version POST /orgs/{org}/teams validation error
site:docs.github.com REST teams create a team permission privacy notification_setting GitHub API version
GitHub REST API Teams create a team permission
https://docs.github.com/en/rest/teams/teams?apiVersion=2022-11-28
'Closing down notice' in https://docs.github.com/en/rest/teams/teams?apiVersion=2022-11-28Source Trail
GitHub source file/reference: