Skip to content

chore(deps): weekly dependency update (2026-10-10) - #11

Merged
robertying merged 2 commits into
mainfrom
deps/update-2026-10-10
Oct 10, 2026
Merged

robertying merged 2 commits into
mainfrom
deps/update-2026-10-10

Conversation

@robertying

Copy link
Copy Markdown
Owner

Summary

Automated weekly dependency update.

  • Updated packageManager pin: pnpm 12.8.1 → 12.11.2 (via corepack use pnpm@latest && corepack install).
  • Ran pnpm update --latest -r across the workspace. Changes:
    • @types/node: 26.6.4 → 26.6.5
    • postcss: 8.5.28 → 8.5.29
    • prettier: 3.9.9 → 3.9.10
    • next / eslint-config-next: 16.3.8 → 16.4.0 (minor)
    • eslint: 9.39.5 → 10.12.0 (major) — kept at latest; eslint-config-next@16.4.0's peer range (eslint: >=9.0.0) and this repo's flat eslint.config.mjs are both compatible, and pnpm lint passes cleanly. No capping was needed for any package.
    • All other dependencies (react, d3, tailwindcss, the typescript/@typescript/typescript6 and @typescript/native aliases, etc.) had no newer versions available and are unchanged.
  • No codegen script exists in this repo — skipped.

Local checks

  • pnpm lint — pass (no issues).
  • pnpm build — pass (Turbopack build, static page generation, and the API-based TypeScript check all succeed).
  • pnpm dev smoke test on port 3000 — pass. Server came up in ~0.5s, the configured / redirect returned 307 to the GPU-trends article page, which rendered with HTTP 200 and the correct <title>. No stack traces or warnings in the startup/request logs.

No fixes were needed beyond the version bumps themselves — nothing broke.

useTypeScriptCli / @typescript/typescript6 workaround assessment

Investigated whether this is still needed, as requested:

  • @typescript/typescript6 is still pinned at 6.0.2 after the update — no newer version exists on the registry (only 6.0.0/6.0.1/6.0.2 are published), and 6.0.2's bin field still only exposes tsc6, not tsc.
  • However, Next 16.4.0 itself changed: reading node_modules/next/dist/lib/typescript/runTypeScriptCli.js, getTypeScriptPackageInfo() now resolves the type-checker binary as bin.tsc, falling back to any bin matching /^tsc\d+$/ (e.g. tsc6) if tsc isn't present. This fallback did not exist when the workaround comment was written.
  • I verified this directly (then reverted before committing — next.config.ts is unchanged in this PR): temporarily setting experimental.useTypeScriptCli: true and running pnpm build succeeded, using the real tsc6 CLI binary end-to-end (compiled, typechecked via the CLI path, generated static pages) with no errors.
  • Assessment: the workaround looks obsolete as of next@16.4.0. It's likely safe to remove useTypeScriptCli: false from next.config.ts (letting it fall back to Next's new default of true) and keep the @typescript/typescript6 alias as-is. I did not flip this myself per instructions — flagging for a human to verify and decide deliberately (worth also re-running the full test/CI suite before removing, in case the CLI-based checker surfaces any errors the API-based checker didn't).

GitHub Actions pins

Checked .github/workflows/CI.yml pins against upstream tags (git ls-remote --tags): actions/checkout@v7 (latest v7.0.1), actions/setup-node@v7 (latest v7.1.0), pnpm/action-setup@v6 (latest v6.1.0), actions/cache@v6 (latest v6.1.0) are all already current — no newer major exists for any of them. No workflow changes made.

Dockerfile

Reviewed Dockerfile. Base image is the floating tag node:lts-alpine — left alone per instructions. No hardcoded/pinned version numbers found in the Dockerfile worth bumping (it relies on corepack enable && corepack install to pick up the packageManager field from package.json, which this PR already updates).

Needs review

Nothing is blocking — all local checks are green. For a human to act on deliberately:

  • Whether to flip useTypeScriptCli to true (or remove the override) in next.config.ts given the assessment above.

🤖 Generated with Claude Code

https://claude.ai/code/session_016juUFzHmFh2gujxhU6nW4z


Generated by Claude Code

Update pnpm packageManager pin to 12.11.2 and bump workspace
dependencies to latest via `pnpm update --latest -r`, including a
major bump of eslint (9.39.5 -> 10.12.0, compatible per
eslint-config-next's `eslint: >=9.0.0` peer range) and a minor bump
of next/eslint-config-next (16.3.8 -> 16.4.0). `pnpm lint` and
`pnpm build` both pass cleanly; dev server smoke-tested on port 3000
with no errors or warnings in the logs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016juUFzHmFh2gujxhU6nW4z
Next 16.4 resolves the aliased @typescript/typescript6 package's tsc6 bin on its own, so the TS API fallback is no longer needed. Verified type errors still fail the build with the flag removed.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016juUFzHmFh2gujxhU6nW4z
@robertying
robertying merged commit 4b5452a into main Oct 10, 2026
2 checks passed
@robertying
robertying deleted the deps/update-2026-10-10 branch October 10, 2026 22:06
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