chore: weekly maintenance — dependency updates & security fixes - #312
Draft
PArns wants to merge 2 commits into
Draft
chore: weekly maintenance — dependency updates & security fixes#312PArns wants to merge 2 commits into
PArns wants to merge 2 commits into
Conversation
next/eslint-config-next/@next/bundle-analyzer 16.2.12 to 16.3.0, @types/node 26.1.2 to 26.2.0, postcss 8.5.25 to 8.5.26, react-intl 10.1.19 to 10.1.20, @types/react 19.2.17 to 19.2.18, @types/react-dom 19.2.3 to 19.2.4. Move tsconfig target off deprecated es5 to ES2017 (type-check only; Next compiles via SWC with noEmit) so the type check passes on the newer toolchain.
Add overrides bumping brace-expansion to >=1.1.18 (1.x) and >=5.0.9, nanoid to >=3.3.17, and sharp to >=0.35.0, clearing all five high advisories from pnpm audit. Bump the pinned @types/react to 19.2.18 and @types/react-dom to 19.2.4 alongside. Regenerate lockfile.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Automated weekly maintenance pass.
Dependency updates (minor/patch within majors)
next: 16.2.12 → 16.3.0eslint-config-next: 16.2.12 → 16.3.0@next/bundle-analyzer: 16.2.12 → 16.3.0@types/node: 26.1.2 → 26.2.0postcss: 8.5.25 → 8.5.26react-intl: 10.1.19 → 10.1.20@types/react: 19.2.17 → 19.2.18 (pinned viapnpm-workspace.yamloverride)@types/react-dom: 19.2.3 → 19.2.4 (pinned via override)Held back on purpose (major bumps):
eslint9.39.5 → 10.8.1framer-motion12.43.0 → 13.0.0typescript6.0.3 → 7.0.2Security (
pnpm audit: 5 high → 0)Fixed via
pnpm.overrides(repo convention):<1.1.18 → >=1.1.18 <2and>=4.0.0 <5.0.9 → >=5.0.9.<3.3.17 → >=3.3.17 <4.<0.35.0 → >=0.35.0 <0.36(next's bundled 0.34.5).pnpm auditafterwards reports no known vulnerabilities.Other changes
tsconfig.json:targetes5→ES2017. TypeScript 6 now errors on the deprecatedes5target (TS5107). The project hasnoEmit: trueand Next compiles via SWC/Turbopack, sotargetonly affects the type-check phase, not shipped output;ES2017matches the Next.js default. Needed to keep the build's TS phase green.Review pass
No further source changes warranted.
target="_blank"links already carryrel="noopener noreferrer";dangerouslySetInnerHTMLuses a static constant; the oneforEach(async …)sits in commented-out dead code. Nothing else worth changing.Verification
pnpm lint— passes (0 errors; 3 pre-existingreact-hooks/exhaustive-depswarnings unchanged).pnpm build— compile + TypeScript pass; static prerender of/[lng]/welcomefails only because this environment lacksCONTENTFUL_*/Google credentials, identical to the pre-change baseline. CI with credentials should build fine.testscript in this repo.Generated by Claude Code