Skip to content

chore: weekly dependency update (2026-09-26) - #8

Merged
robertying merged 1 commit into
mainfrom
deps/update-2026-09-26
Sep 27, 2026
Merged

robertying merged 1 commit into
mainfrom
deps/update-2026-09-26

Conversation

@robertying

Copy link
Copy Markdown
Owner

Summary

Weekly automated dependency update. Ran corepack use pnpm@latest then pnpm update --latest -r.

Bumped:

  • pnpm packageManager: 12.4.1 -> 12.6.0
  • next: 16.3.5 -> 16.3.6 (patch, but see workaround note below — behavior-relevant)
  • eslint-config-next: 16.3.5 -> 16.3.6 (follows next)
  • @types/node: 26.4.1 -> 26.6.3
  • csv-parse: 7.0.2 -> 7.0.3
  • fs-extra: 11.4.0 -> 11.4.1
  • prettier: 3.9.6 -> 3.9.9

Capped back down: eslint resolved to 10.11.0 by pnpm update --latest, but I capped it back to 9.39.5 (the latest 9.x release) in package.json. Reason: eslint-plugin-react@7.37.5 (pulled in transitively through eslint-config-next, which is pinned to next's version) throws TypeError: contextOrFilename.getFilename is not a function under eslint 10 — this is an eslint-plugin-react/eslint-config-next support gap for eslint 10, not an app bug. All other deps in this repo (react, next, typescript aliases, d3, tailwind, etc.) were already at their latest versions before this update and had no newer release this cycle.

Checks

  • pnpm lint — pass (clean, after the eslint cap above; failed with the getFilename TypeError before capping)
  • pnpm build — pass (Turbopack build + TypeScript check via next build, no errors)
  • pnpm dev smoke test — pass. Port 3000 was occupied so it bound 3001; curl showed / returning a 307 redirect and the destination article slug (/adaptation-and-adoption-analyzing-gpu-trends-among-pc-gamers-during-covid-19-and-crypto-craze) returning 200 with real rendered content (verified via page <title>). No stack traces or warnings in dev startup logs beyond the expected useTypeScriptCli experimental notice (see below). Note: next dev auto-generated AGENTS.md/CLAUDE.md scaffold files (a new Next 16 dev-server feature) — these were removed before committing since they're unrelated to this update.

What I fixed and why it was safe

  • Capped eslint to 9.39.5 as described above — purely a version-compat gap in a linked plugin, no source changes needed, and it's the newest release still compatible with the current eslint-config-next/eslint-plugin-react chain.
  • No other code changes were needed; lint and build were otherwise clean against the updated deps.

useTypeScriptCli workaround — obsolescence check

next.config.ts currently sets experimental.useTypeScriptCli: false with a comment explaining that the aliased typescript package (@typescript/typescript6) only ships lib/typescript.js, not a tsc binary Next's CLI type-checker could invoke.

This update lands the repo on next@16.3.6, which (per two sibling repos in this update batch, "thursday" and "blog") adds a /^tsc\d+$/ bin-name fallback to runTypeScriptCli.js. I verified this directly in this repo:

  • node_modules/next/dist/lib/typescript/runTypeScriptCli.js at 16.3.6 does contain the fallback: Object.entries(packageJson.bin ?? {}).find(([name]) => /^tsc\d+$/.test(name)).
  • @typescript/typescript6@6.0.2's own package.json declares "bin": { "tsc6": "./bin/tsc6" }, which matches that regex.
  • I temporarily flipped useTypeScriptCli: true locally, ran rm -rf .next && pnpm build, and it compiled and type-checked successfully with no ⨯ useTypeScriptCli warning (vs. the warning that appears with the flag off). I then reverted the config change before committing — next.config.ts is unchanged in this PR.

Conclusion: the workaround now looks safe to remove (i.e. useTypeScriptCli could be flipped to true or the override dropped entirely to take Next's new default). I did not make that change here per instructions — flagging it for a maintainer to decide, since it's a config/behavior change outside the scope of a routine dependency bump.

GitHub Actions pins (CI.yml)

Checked live tags for all four pinned actions:

  • actions/checkout@v7 — latest major tag, currently at v7.0.1. No change needed.
  • actions/setup-node@v7 — latest major tag, currently at v7.0.0. No change needed.
  • pnpm/action-setup@v6 — latest major tag (no v7 exists), currently at v6.1.0. No change needed.
  • actions/cache@v6 (used twice) — latest major tag, currently at v6.1.0. No change needed.

All four are already tracking their latest available major version tag (which auto-resolves to the newest minor/patch), matching what sibling repos found this week. No CI.yml changes made.

Dockerfile

FROM node:lts-alpine is an intentional floating tag — left alone. corepack enable && corepack install picks up the bumped packageManager pin automatically. No other hardcoded/pinned versions found in the Dockerfile.

Needs review

  • useTypeScriptCli workaround removal (see above) — empirically verified safe, but left as a follow-up decision rather than bundled into this dependency-update PR.
  • eslint version cap (9.39.5 instead of resolved 10.11.0) — should be revisited once eslint-plugin-react (or eslint-config-next) ships eslint 10 support.
  • Pre-existing (not introduced by this PR): pnpm peers check reports react-popper@2.3.0 wanting react/react-dom ^16.8.0 || ^17 || ^18 while the repo runs React 19.3.0. This predates this update (react/react-dom versions unchanged) and wasn't touched.

🤖 Generated with Claude Code

https://claude.ai/code/session_018cQGMQEWosyap8seKE16Be


Generated by Claude Code

Bump pnpm packageManager to 12.6.0 and update workspace deps via
`pnpm update --latest -r`.

Notable bumps:
- next 16.3.5 -> 16.3.6
- eslint-config-next 16.3.5 -> 16.3.6
- @types/node 26.4.1 -> 26.6.3
- csv-parse 7.0.2 -> 7.0.3
- fs-extra 11.4.0 -> 11.4.1
- prettier 3.9.6 -> 3.9.9

eslint capped back to 9.39.5 (latest 9.x) instead of the resolved
10.11.0: eslint-plugin-react@7.37.5 (pulled in transitively via
eslint-config-next) throws
`TypeError: contextOrFilename.getFilename is not a function` under
eslint 10, which is an eslint-plugin-react/eslint-config-next support
gap, not an app bug.

Verified: `pnpm lint` and `pnpm build` pass cleanly; `pnpm dev` smoke
test confirmed the `/` redirect resolves to the article page with
real content (200).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018cQGMQEWosyap8seKE16Be
@robertying
robertying merged commit 5b9fd2c into main Sep 27, 2026
2 checks passed
@robertying
robertying deleted the deps/update-2026-09-26 branch September 27, 2026 03:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants