Make dependabot ignore major version upgrades to @types/node#291
Make dependabot ignore major version upgrades to @types/node#291
Conversation
Node 25 is a non-LTS release, so @types/node v25 would create a mismatch with our Node 24 LTS runtime. This rule prevents dependabot from proposing major version bumps while still allowing patch/minor updates within v24.x. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe pull request adds a Dependabot ignore rule to the npm ecosystem configuration in 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Overview
Adds a dependabot ignore rule to skip major version bumps for
@types/node. This avoids dependabot PRs like #289 that propose upgrading@types/nodeto the 25.X.X branch. This would create a type/runtime mismatch with our Node 24 LTS target. Patch/minor updates within v24.x will still be proposed.Checklist
yarn buildand committed resulting changes..github/workflows/test.ymlor explained why it doesn't make sense to do so.Important
After merging, make sure to create a new GitHub release and associated tag for this release.
You can either create the tag locally and then create a corresponding GitHub release,
or just create both the tag and release using the GitHub Release UI.
Additionally, if this is not a breaking change, make sure to update the
v1tag: