Versioned API schema

GitHub REST API repository use_squash_pr_title_as_default deprecated field removed

Generated client/model validation fails because a deprecated response field is gone.

GitHub REST APIDeveloper platform APIVersioned API schemagh_rest2026

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: Repository settings reader expects use_squash_pr_title_as_default
Likely root cause: Generated client/model validation fails because a deprecated response field is gone.
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

Generated client/model validation fails because a deprecated response field is gone.

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 repository use_squash_pr_title_as_default deprecated field removed
"use_squash_pr_title_as_default" GitHub
"squash_merge_commit_title" "use_squash_pr_title_as_default"
"use_squash_pr_title" GitHub REST API
docs.github.com REST repos update repository squash_merge_commit_title PR_TITLE
"squash_merge_commit_title" "docs.github.com"
https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28
'use_squash_pr_title_as_default' in https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28

Source Trail

GitHub source file/reference: