Repository navigation
fix: keep the certified SDK baseline out of unattended updates - #24
Merged
Merged
Conversation
Dependabot classifies @cursor/sdk 1.0.23 -> 1.0.40 as a semver patch, so the npm-patch group swept the exact pin into #4 even though the config says the certified baseline is not automated. Add an ignore block for the SDK, the undici override, and @types/node majors so the stated policy is enforced rather than merely described.
This was referenced Oct 23, 2026
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
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.
Why
Dependabot opened #4 with
@cursor/sdk1.0.23 -> 1.0.40 because 1.0.x -> 1.0.y is a semver patch, so thenpm-patchgroup's*pattern swept the exact pin in. The config comment already said the certified baseline is deliberately not automated, but a comment does not constrain the matcher; #4 fails the bridge and package lanes that assert the pin.What
ignoreentries for the npm ecosystem:@cursor/sdk- the certified baseline moves only through a deliberate, re-certified upgrade (the 1.0.40 closure also drops@connectrpc/connect-nodeand adds azodpeer, so it is not a mechanical patch).undici- the6.28.1override is a release decision.@types/nodemajors - types must describe the oldest supported runtime (engines >=22.13, CI Node 22.22.3), not a newer one; this also prevents recurrence of build(deps-dev): bump @types/node from 22.20.1 to 26.6.3 in /bridge-node #6.Security updates are unaffected: Dependabot security updates do not use these version-update ignore rules.
Evidence
python3 -c 'yaml.safe_load(...)'parses the file; the npm entry round-trips with the three ignore rules and both groups intact.