From 6dc2b631bd28626417645cb7eb898534cffed0f5 Mon Sep 17 00:00:00 2001 From: Joost de Valk Date: Sat, 8 Aug 2026 12:26:39 +0200 Subject: [PATCH] docs(deps): correct the stale rationale on the /mcp workers-types ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The note claimed "wrangler's peer range only accepts workers-types v4; a v5 bump breaks `npm ci`", and told the reader to re-allow the update once wrangler accepted v5. Both parts have expired: wrangler 4.118.0 peers @cloudflare/workers-types "^5.20260730.1", and /mcp has been on 5.x for a while — #152 and #168 both landed v5 bumps. Taken at face value the note said this hold was finished and the rule could be deleted. It cannot. The rule is what stops a workers-types major landing ahead of wrangler's peer range, which is the same ERESOLVE failure one major later. What was wrong was framing a standing guard as a temporary hold pinned to specific versions, so it rotted the moment the ecosystem moved. Rewritten to describe the mechanism rather than a version, to say explicitly that it is standing, to note that wrangler moves the range itself and the major here should be bumped alongside it, and to date the version-specific observation and give the command that re-checks it (`npm view wrangler peerDependencies`) so the next reader verifies rather than trusts. Comments only — the parsed rules are unchanged, verified by diffing the YAML. No behaviour change. Co-Authored-By: Claude Opus 5 (1M context) --- .github/dependabot.yml | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 7211ca77..65527a45 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -35,9 +35,16 @@ updates: day: monday open-pull-requests-limit: 5 ignore: - # wrangler's peer range only accepts workers-types v4; a v5 bump - # breaks `npm ci` in the Deploy MCP workflow. Re-allow once - # wrangler's peerDependencies accept v5. + # Standing rule, not a temporary hold: wrangler peers + # @cloudflare/workers-types to one specific major, so a workers-types + # major that lands before wrangler catches up fails `npm ci` with + # ERESOLVE and takes the Deploy MCP workflow with it. Minor and patch + # bumps within the current major are unaffected and still flow. + # Wrangler moves this range itself; when it does, bump the major here + # by hand in the same PR as the wrangler bump. Check with: + # npm view wrangler peerDependencies + # (2026-08-08: wrangler 4.118.0 peers ^5.x and /mcp is on 5.x — the + # v4 constraint this rule was originally written for is long gone.) - dependency-name: "@cloudflare/workers-types" update-types: ["version-update:semver-major"]