Fix dependency scanner flagging @types/node major updates#10
Fix dependency scanner flagging @types/node major updates#10google-labs-jules[bot] wants to merge 1 commit intomainfrom
Conversation
Major version updates for @types/node usually correspond to the Node.js runtime version. Projects pinned to a specific Node.js major version (e.g. 20) should not be prompted to update to a newer major version of types (e.g. 25) as it is not a standard library update. This change downgrades the severity of such updates to "none". Added a regression test in lib/dependencies.test.ts.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Suppressed major update warnings for
@types/nodein the dependency scanner.This ensures that users pinned to a specific Node.js LTS version (e.g., Node 20) are not incorrectly warned about "Major Updates" when a newer Node.js version (e.g., Node 22 or 25) is released, as the types package version mirrors the runtime version.
Added
lib/dependencies.test.tsto verify this behavior and prevent regressions.PR created automatically by Jules for task 6644883061518400127 started by @bmccall17