gh pr edit fails before applying changes because deprecated Projects Classic query errors.

Reported (UTC): 2026-07-16 08:42

What was being attempted: After rebasing and force-pushing BuildTestEmbedded PR https://github.com/CodexCoder21Organization/BuildTestEmbedded/pull/335, update its title and body to change the release coordinate from 0.0.319 to 0.0.320.

What went wrong: gh pr edit 335 --repo CodexCoder21Organization/BuildTestEmbedded --title 'Pin warmcache-v4 image for runner 0.0.64 (release 0.0.320)' --body '<updated body>' exited nonzero 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). A subsequent gh pr view confirmed neither title nor body changed.

Impact: The normal authenticated CLI path cannot update PR metadata, so task-critical release-coordinate text silently remains stale unless the failure is noticed and worked around.

Workaround used: Read the PR body with gh pr view, replace the stale coordinate locally, then PATCH repos/CodexCoder21Organization/BuildTestEmbedded/pulls/335 through gh api, which does not query Projects Classic.

Suggested durable fix: Upgrade or patch the installed gh CLI so gh pr edit no longer requests repository.pullRequest.projectCards, or change organizational automation guidance to use the REST pulls PATCH endpoint for metadata edits until the shared CLI is upgraded.

Production verification — 2026-07-17

Status: STILL EXISTS. The current image still ships gh 2.23.0, while the upstream project-data fix remains open, so the deprecated Projects Classic query path is still present.

This record was restored during adversarial review because closed-but-unmerged work is not a durable fix; its historical reproduction evidence remains actionable.