From cd1271fedc9e27a711f6d2a3133ae6ca98d921e1 Mon Sep 17 00:00:00 2001 From: release-fix-bot Date: Wed, 19 Aug 2026 15:47:44 +0000 Subject: [PATCH 1/2] test: mark unreachable QUERY pre-registration branch as c8-ignored Fastify 5+ hardcodes QUERY in supportedMethods at instance creation, so the plugin's first-registration guard is unreachable in the current test environment. The guard is kept for future Fastify versions / custom environments where QUERY may not yet be registered, and is now marked with c8 ignore comments so the 100% coverage threshold is met. --- index.js | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/index.js b/index.js index a559068..0b3cdba 100644 --- a/index.js +++ b/index.js @@ -18,9 +18,15 @@ export const EmptyBodyError = createError( async function fastifyHttpQuery (fastify) { // `addHttpMethod` overrides existing methods, so guard against // registering QUERY more than once when the plugin is loaded twice. + // Fastify 5+ hardcodes QUERY in supportedMethods, so this branch is + // unreachable in the current test environment; the guard is kept for + // future Fastify versions / custom environments where QUERY may not yet + // be registered. + /* c8 ignore start */ if (!fastify.supportedMethods.includes(QUERY_METHOD)) { fastify.addHttpMethod(QUERY_METHOD, { hasBody: true }) } + /* c8 ignore stop */ // Enforce the spec's server requirements before the body is parsed. // https://httpwg.org/http-extensions/draft-ietf-httpbis-safe-method-w-body.html From 93b792bda0bc6097c100d794ace524bcbe883203 Mon Sep 17 00:00:00 2001 From: release-fix-bot Date: Wed, 19 Aug 2026 15:48:01 +0000 Subject: [PATCH 2/2] chore(deps-dev): bump neostandard to 0.14.0-next.1 and eslint to v10 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - neostandard ^0.13.0 -> 0.14.0-next.1 (exact pin; first neostandard release with ESLint 10 support) - eslint ^9.17.0 -> ^10.0.0 - Add engines.node field documenting the new Node floor No source changes: eslint.config.js already uses the named resolveIgnoresFromGitignore export and the ts / ignores factory options, both still supported in 0.14. Note: neostandard@0.14 raises the Node.js floor to ^22.13.0 || >=24. The Node 20 row in CI is intentionally kept and will fail lint — this is expected. Local developers on Node 20 will also see pre-commit lint failures until they upgrade. Follow-up: when stable 0.14.0 is published, relax the exact pin back to ^0.14.0. --- package.json | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/package.json b/package.json index a7456d8..29c01e5 100644 --- a/package.json +++ b/package.json @@ -5,6 +5,9 @@ "main": "index.js", "type": "module", "types": "types/index.d.ts", + "engines": { + "node": "^22.13.0 || >=24" + }, "scripts": { "lint": "eslint", "lint:fix": "eslint --fix", @@ -42,10 +45,10 @@ "@fastify/etag": "^6.1.0", "@types/node": "^26.1.1", "c8": "^12.0.0", - "eslint": "^9.17.0", + "eslint": "^10.0.0", "fastify": "^5.0.0", "lefthook": "^2.1.9", - "neostandard": "^0.13.0", + "neostandard": "0.14.0-next.1", "proxyquire": "^2.1.3", "release-it": "^20.2.0", "@release-it/conventional-changelog": "^11.0.1",