Repository navigation
chore(deps): weekly dependency update (2026-10-10) - #11
Merged
Merged
Conversation
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
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
Automated weekly dependency update.
packageManagerpin: pnpm12.8.1→12.11.2(viacorepack use pnpm@latest && corepack install).pnpm update --latest -racross the workspace. Changes:@types/node:26.6.4→26.6.5postcss:8.5.28→8.5.29prettier:3.9.9→3.9.10next/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 flateslint.config.mjsare both compatible, andpnpm lintpasses cleanly. No capping was needed for any package.typescript/@typescript/typescript6and@typescript/nativealiases, etc.) had no newer versions available and are unchanged.Local checks
pnpm lint— pass (no issues).pnpm build— pass (Turbopack build, static page generation, and the API-based TypeScript check all succeed).pnpm devsmoke 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/typescript6workaround assessmentInvestigated whether this is still needed, as requested:
@typescript/typescript6is still pinned at6.0.2after the update — no newer version exists on the registry (only6.0.0/6.0.1/6.0.2are published), and6.0.2'sbinfield still only exposestsc6, nottsc.node_modules/next/dist/lib/typescript/runTypeScriptCli.js,getTypeScriptPackageInfo()now resolves the type-checker binary asbin.tsc, falling back to any bin matching/^tsc\d+$/(e.g.tsc6) iftscisn't present. This fallback did not exist when the workaround comment was written.next.config.tsis unchanged in this PR): temporarily settingexperimental.useTypeScriptCli: trueand runningpnpm buildsucceeded, using the realtsc6CLI binary end-to-end (compiled, typechecked via the CLI path, generated static pages) with no errors.next@16.4.0. It's likely safe to removeuseTypeScriptCli: falsefromnext.config.ts(letting it fall back to Next's new default oftrue) and keep the@typescript/typescript6alias 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.ymlpins against upstream tags (git ls-remote --tags):actions/checkout@v7(latestv7.0.1),actions/setup-node@v7(latestv7.1.0),pnpm/action-setup@v6(latestv6.1.0),actions/cache@v6(latestv6.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 tagnode:lts-alpine— left alone per instructions. No hardcoded/pinned version numbers found in the Dockerfile worth bumping (it relies oncorepack enable && corepack installto pick up thepackageManagerfield frompackage.json, which this PR already updates).Needs review
Nothing is blocking — all local checks are green. For a human to act on deliberately:
useTypeScriptClitotrue(or remove the override) innext.config.tsgiven the assessment above.🤖 Generated with Claude Code
https://claude.ai/code/session_016juUFzHmFh2gujxhU6nW4z
Generated by Claude Code