Repository navigation
Weekly dependency update (2026-10-03) - #10
Merged
Merged
Conversation
- Bump packageManager pin to pnpm@12.8.1 - Bump next and eslint-config-next to 16.3.8 (patch) - Bump @types/node to 26.6.4 (patch) - eslint attempted bump to 10.12.0 but capped back to 9.39.5 (latest 9.x): eslint-plugin-react@7.37.5 (pulled in transitively via eslint-config-next) breaks under eslint 10's new rule-context API (TypeError: contextOrFilename.getFilename is not a function), eslint-plugin-import and eslint-plugin-jsx-a11y also only declare peer support up to eslint ^9. No upstream fix available yet. - lint and build verified clean; lodash modularizeImports and the redirects() config both verified working (smoke tested against the standalone server output used by the Dockerfile) - GitHub Actions in CI.yml already at latest major tags (checkout@v7, setup-node@v7, action-setup@v6, cache@v6); no change needed Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WezYgpH2MCQBQQBrhpnURZ
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.
Summary
Weekly automated dependency update.
packageManagerpin: pnpm12.6.0→12.8.1(viacorepack use pnpm@latest && corepack install).pnpm update --latest -r. Most dependencies were already at latest (updated last week in chore: weekly dependency update (2026-09-26) #8). Resulting changes:next16.3.6 → 16.3.8 (patch)eslint-config-next16.3.6 → 16.3.8 (patch)@types/node26.6.3 → 26.6.4 (patch)eslint9.39.5 → 10.12.0 attempted (major), capped back down to 9.39.5Major bump capped back down
eslintwas updated to the new major10.12.0bypnpm update --latest, but this brokepnpm lint:Root cause:
eslint-plugin-react@7.37.5(pulled in transitively througheslint-config-next) calls an ESLint rule-context API that eslint 10 removed/changed.eslint-plugin-import@2.32.0andeslint-plugin-jsx-a11y@6.10.2(also transitive, viaeslint-config-next) likewise only declare peer support up toeslint ^9, confirmed viapnpm peers check. This is not a code bug in this repo — it's upstream tooling not yet supporting eslint 10. I cappedeslintback to9.39.5, the latest release in the 9.x line (unchanged from before this PR), untileslint-config-next's plugin deps add eslint 10 support.Local checks
pnpm install(after pin): passpnpm run lint: pass (clean, after capping eslint to 9.39.5)pnpm run build: pass (Next 16.3.8, Turbopack, TypeScript check vianext buildall succeeded)output: "standalone", same as the Dockerfile uses) and rannode .next/standalone/server.json a free port.GET /returned307to/adaptation-and-adoption-analyzing-gpu-trends-among-pc-gamers-during-covid-19-and-crypto-craze(confirmsredirects()innext.config.tsstill works), and following it returned200with the expected page title and no errors/warnings in server logs.lodashmodularizeImports: config targets thelodashpackage, but the codebase only imports fromlodash-es(@types/lodash-esis the only lodash-related devDependency; there's no plainlodashdependency). This mismatch pre-dates this PR and isn't something this update changed — flagging it since the task asked me to pay attention to it, but leaving it alone as out of scope for a dependency bump..github/workflows/CI.yml: checkedactions/checkout,actions/setup-node,pnpm/action-setup,actions/cacheagainst their latest tags — all four are already pinned at their latest major (checkout@v7,setup-node@v7,action-setup@v6,cache@v6). No workflow changes needed.node:lts-alpineis a floating tag, left as-is per instructions. No other hardcoded versions found worth bumping.useTypeScriptCli: falseworkaround (next.config.ts)Still necessary. The project's
typescriptdependency is aliased tonpm:@typescript/typescript6@6.0.2, and that package'spackage.jsononly declaresbin: { "tsc6": "./bin/tsc6" }— still notscbinary. (There is atscbinary innode_modules/.bin, but it comes from the separate@typescript/nativedependency, aliased totypescript@7.0.2, which is unrelated to thetypescriptimport alias Next's CLI type-checker resolves.) No change recommended; the workaround comment innext.config.tsremains accurate.Needs review
None — nothing left broken. The only item requiring upstream action is
eslint-config-next's plugin dependencies adding eslint 10 support, at which point theeslintpin above can be lifted.🤖 Generated with Claude Code
https://claude.ai/code/session_01WezYgpH2MCQBQQBrhpnURZ
Generated by Claude Code