chore(deps): update npm dependencies and enable dependabot - #11
Merged
Merged
Conversation
This repo had no dependabot config, so nothing was watching it. The AWS SDK had drifted 371 minor versions behind and 'npm audit' reported 19 vulnerabilities (1 critical, 1 high, 17 moderate), all in the @aws-sdk/* chain. After the update: 0 vulnerabilities. - @aws-sdk/client-s3 3.750.0 -> 3.1121.0 - eslint 10.2.0 -> 10.9.1 - prettier 3.8.1 -> 3.9.6 - typescript-eslint 8.58.0 -> 8.69.0 - typescript floor raised 5.4.0 -> 5.9.3 (stays on 5.x, see below) Adds .github/dependabot.yml with weekly npm + github-actions updates so this cannot silently rot again. Two majors are explicitly ignored with the reason recorded in the config: - @types/node stays on ^20 to match the oldest Node in the CI matrix. - typescript stays on 5.x: typescript-eslint peers '>=4.8.4 <6.1.0', and no @types/node release supports TS 6 yet (its typesVersions caps at '<=5.6'), so tsc fails to resolve node globals under v6. Verified: npm ci clean, tsc build clean, 8/8 tests pass, eslint clean with --max-warnings 0, and @aws-sdk/client-s3 loads at runtime.
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.
Why this one matters
This repo had no
.github/dependabot.yml, so nothing was watching it.@aws-sdk/client-s3had drifted from 3.750.0 to 371 minor versions behind, andnpm auditreported 19 vulnerabilities — 1 critical, 1 high, 17 moderate — all in the@aws-sdk/*chain. After this update: 0 vulnerabilities.Dependabot config
Adds weekly
npm+github-actionsupdates so this cannot silently rot again. Two majors are ignored, with the reason recorded inline in the config rather than left for the next person to rediscover:@types/nodestays on^20— it should track the oldest Node in the CI matrix (20), not the newest release. Bumping it would type-check against APIs the supported runtime does not have.typescriptstays on 5.x —typescript-eslint@8.69.0declarespeer typescript: >=4.8.4 <6.1.0, and DefinitelyTyped has shipped no@types/nodesupporting TS 6 (itstypesVersionscaps at<=5.6). I tried v6:tscfails with 12TS2591/TS2304errors because it cannot resolveprocess,node:pathorfetch.Verification (local)
npm ciclean,tscbuild clean,npm test8/8 passed,eslint . --max-warnings 0clean,npm audit0 vulnerabilities, and@aws-sdk/client-s3confirmed to load at runtime against thenpm citree.The committed
build/output is byte-identical after rebuilding, so it is not part of this diff.