From 0de9e539d51e12902b5b7479a8f084b971ec255f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Conejo?= Date: Wed, 11 Nov 2026 06:51:53 +0100 Subject: [PATCH] fix(github): send API version 2026-03-10 before 2022-11-28 retires After that date the WordPress release announcement job gets 410 Gone from GitHub when it checks for or creates the wordpress@ release, so releases stop being recorded. This sends X-GitHub-Api-Version 2026-03-10 from the one shared githubRequest helper; the code only reads the response status and posts fields that the listed 2026-03-10 breaking changes do not touch. --- scripts/announce-wordpress-release.mjs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/announce-wordpress-release.mjs b/scripts/announce-wordpress-release.mjs index 5f1246d..c8664d3 100644 --- a/scripts/announce-wordpress-release.mjs +++ b/scripts/announce-wordpress-release.mjs @@ -87,7 +87,7 @@ const githubRequest = ({ token, repository, method, pathname, body }) => headers: { accept: 'application/vnd.github+json', authorization: `Bearer ${token}`, - 'x-github-api-version': '2022-11-28', + 'x-github-api-version': '2026-03-10', ...(body === undefined ? {} : { 'content-type': 'application/json' }), }, ...(body === undefined ? {} : { body: JSON.stringify(body) }),