docs(deps): correct the stale rationale on the /mcp workers-types ignore - #170
Merged
Conversation
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) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
6dc2b63
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://ae42da2f.specification-website.pages.dev |
| Branch Preview URL: | https://docs-dependabot-mcp-ignore-n.specification-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #167. Comments only — the parsed Dependabot rules are unchanged.
What was wrong
The note on the
/mcpignore read:Both halves have expired:
Locally,
wrangler@4.118.0peers^5.20260730.1, and/mcpis on5.20260804.1— #152 and #168 both landed v5 bumps this week.Why the rule still has to stay
Read literally, the note said the hold was finished and the rule could be deleted. It cannot. It is what stops a workers-types major landing ahead of whatever major wrangler currently peers — the identical
ERESOLVEfailure, one major later. (No v6 exists yet; published majors are 0–5.)The actual defect was framing a standing guard as a temporary hold pinned to specific version numbers, which guaranteed it would rot as soon as the ecosystem moved — and it did, silently, while still looking authoritative.
The rewrite
npm view wrangler peerDependenciesso the next reader verifies instead of trusting.Verified
Parsed the YAML before and after: both files yield
[{"dependency-name":"@cloudflare/workers-types","update-types":["version-update:semver-major"]}]Diffing the change with comment lines stripped leaves nothing, so behaviour is identical.
format:checkpasses.🤖 Generated with Claude Code