Skip to content

build(deps): @types/node 26.6.5 (Node 26 types) - #50

Merged
evereq merged 1 commit into
developfrom
build/types-node-26
Oct 25, 2026
Merged

evereq merged 1 commit into
developfrom
build/types-node-26

Conversation

@evereq

@evereq evereq commented Oct 24, 2026

Copy link
Copy Markdown
Member

Moves the Node type definitions to the Node 26 line, matching the Node 26.12.1 API image (NN #17: Node and @types/node move together).

file old new
package.json devDependencies @types/node ^25.0.9 ^26.6.5
yarn.lock @types/node@^26.6.5 (was 25.0.9 via ^25.0.9) 26.6.5 (new entry)
yarn.lock undici-types@~8.9.0 — 8.9.0 (new entry)
  • Lockfile: yarn 1.22.22 (the packageManager pin), yarn install --ignore-scripts; nothing else moved (@types/node@* for transitive users stays on 25.0.9). The two new resolved URLs point at registry.npmjs.org, like the rest of the file.
  • TypeScript stays at 5.9.3 (@types/node 26 needs >= 5.6).
  • Checks (local): tsc --noEmit -p tsconfig.json and -p tsconfig.build.json: exit 0 with @types/node 26.6.5 + TypeScript 5.9.3. The dev image build (push to develop) builds it on Node 26.12.1.
  • Not deployed anywhere (the DigitalOcean deploy is gated by DO_ENABLED).

Rollback: revert the merge commit.

🤖 Generated with Claude Code

devDependencies @types/node ^25.0.9 -> ^26.6.5. yarn.lock (yarn 1.22.22,
`yarn install --ignore-scripts`): new entries @types/node@^26.6.5 -> 26.6.5
and undici-types@~8.9.0 -> 8.9.0 only (resolved host set to
registry.npmjs.org like the rest of the file). TypeScript stays 5.9.3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 24, 2026 20:44
@coderabbitai

coderabbitai Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 70b44f33-b508-45f2-bc5d-fc5da951f7b1
Commits

Reviewing files that changed from the base of the PR and between f0b5108 and d131354.

Files ignored due to path filters: 1
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing: 1
  • package.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Summary by CodeRabbit

  • Chores
    • Updated development tooling. There are no changes to app features or behavior in this release.

Walkthrough

The @types/node development dependency requirement in package.json changes from ^25.0.9 to ^26.6.5.

Changes

Node.js Type Definitions

Layer / File(s) Summary
Update Node.js type requirement
package.json
The @types/node development dependency requirement changes from ^25.0.9 to ^26.6.5.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Possibly related PRs

Suggested reviewers: adkif

Merge Risk: Minimal · up to d1313

The Node.js type dependency update is mergeable with normal checks.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly identifies the dependency update from @types/node 25 to version 26.6.5 and matches the main change.
Description check Passed The description accurately explains the @types/node update, lockfile changes, compatibility details, validation results, deployment status, and rollback plan.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Some tools did not complete. Review the errors below.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

package.json

Oops! Something went wrong! :(

ESLint: 9.39.2

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './@typescript-eslint' is not defined by "exports" in /node_modules/eslint-config-prettier/package.json
Referenced from: /.eslintrc.js
at exportsNotFound (node:internal/modules/esm/resolve:315:10)
at packageExportsResolve (node:internal/modules/esm/resolve:663:9)
at resolveExports (node:internal/modules/cjs/loader:754:36)
at Module._findPath (node:internal/modules/cjs/loader:821:31)
at Module._resolveFilename (node:internal/modules/cjs/loader:1557:27)
at wrapResolveFilename (node:internal/modules/cjs/loader:1118:27)
at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1169:12)
at require.resolve (node:internal/modules/helpers:175:31)
at Object.resolve (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2447:46)
at ConfigArrayFactory._loadExtendedShareableConfig (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3383:33)
(node:2) ESLintRCWarning: You are using an eslintrc configuration file, which is deprecated and support will be removed in v10.0.0. Please migrate to an eslint.config.js file. See https://eslint.org/docs/latest/use/configure/migration-guide for details. An eslintrc configuration file is used because you have the ESLINT_USE_FLAT_CONFIG environment variable set to false. If you want to use an eslint.config.js file, remove the environment variable. If you want to find the location of the eslintrc configuration file, use the --debug flag.
(Use node --trace-warnings ... to show where the warning was created)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit checks the version line,
New Node types now sit in place.
The package file records the change,
No extra carrots need a chase.
Ears twitch; the update is complete.

Comment @coderabbitai help to get the list of available commands.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The major typings upgrade needs human confirmation of package artifacts and the reported compiler checks, which could not be independently verified.

No open issues 🎉

What changed in this PR

Updates Node.js type definitions to the Node 26 line to align with the API image described in the PR.

Changes:

  • Bumps @types/node from ^25.0.9 to ^26.6.5.
  • Adds lockfile entries for @types/node 26.6.5 and undici-types 8.9.0, preserving the existing wildcard resolution.
File Description
yarn.lock Locks the new type packages while retaining existing transitive resolutions.
package.json Updates the direct Node.js type dependency to ^26.6.5.

Review effort: Balanced

@greptile-apps

greptile-apps Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The PR appears safe to merge; no actionable issue was established.

Summary

Updates @types/node from ^25.0.9 to ^26.6.5, matching the Node 26 Docker images.

  • The API build now type-checks against Node 26 definitions.

Reviews (1) · Last reviewed commit: "build(deps): @types/node 26.6.5 (Node 26..." · Reviewed by Greptile

@evereq

evereq commented Oct 24, 2026

Copy link
Copy Markdown
Member Author

NN #18 review: CodeRabbit = no actionable comments (it excludes yarn.lock; I reviewed the lock diff myself: only the new @types/node@^26.6.5 → 26.6.5 and undici-types@~8.9.0 → 8.9.0 entries, resolved on registry.npmjs.org, @types/node@* unchanged). Greptile 5/5 (low impact). Copilot overview: no open issues; its "needs a closer look" asks to confirm the compiler checks: tsc --noEmit on tsconfig.json + tsconfig.build.json exit 0 locally with @types/node 26.6.5 / TS 5.9.3, and the develop image build compiles it again on Node 26.12.1 after merge. DeepScan, Cspell, Snyk, CodeQL default setup green. Analyze (javascript) red = pre-existing: the legacy codeql-analysis.yml (CodeQL Action v2, SARIF rejected) fails on every run since 2026-07-19, e.g. develop https://github.com/ever-co/ever-api-starter-kit/actions/runs/40006815500 . Merging with --admin once homelab egress is back to normal.

@evereq
evereq merged commit 63117a0 into develop Oct 25, 2026
13 of 14 checks passed
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