gh pr edit fails because the installed client queries retired Projects classic fields

Reported (UTC): 2026-07-16 13:51

What was being attempted: update the body of an existing BuildTestEmbedded pull request after a required rebase and successful CI run.

What went wrong: gh pr edit 337 --repo CodexCoder21Organization/BuildTestEmbedded --body-file - failed before applying the edit with the exact error: GraphQL: Projects (classic) is being deprecated in favor of the new Projects experience, see: https://github.blog/changelog/2024-05-23-sunset-notice-projects-classic/. (repository.pullRequest.projectCards). The body input was valid and the PR remained otherwise accessible through gh pr view.

Impact: normal PR metadata maintenance is blocked on this host, and an agent could incorrectly assume the edit was applied unless it checks the exit code and re-reads the PR.

Workaround used: read the current body with gh pr view and PATCH the pull request body through repos/{owner}/{repo}/pulls/{number} using gh api, which does not query projectCards.

Suggested durable fix: upgrade the installed GitHub CLI to a release that no longer requests the retired projectCards field, or adjust the shared gh configuration/wrapper so gh pr edit uses the REST pull-request update endpoint.

Production verification — 2026-07-17

Status: STILL EXISTS. The current image still ships gh 2.23.0. A fresh gh repo clone produced an HTTPS origin whose git fetch failed non-interactively, and neither repository-local nor global Git author identity was configured before this audit.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.