chore(deps-dev): bump @types/node from 26.6.3 to 26.6.4 in the development-dependencies group

[dependabot]

Bumps the development-dependencies group with 1 update: @types/node.

Updates @types/node from 26.6.3 to 26.6.4

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[kschlt]

PR Review Verdict

Result: PASS

Deterministic: Measured on head e8a219e — tree 3b74a3e. The base recorded on the pull request is 70f7e62, which is origin/main as of this measurement, and the branch is one commit on top of it, so the head is the merge result and there is nothing to merge; GitHub reports clean and all 22 check runs green. In a fresh worktree with npm ci run before anything else, under Node 26.10.0 against a real PostgreSQL 16: tsc --noEmit exits 0, biome ci . exits 0, and vitest run is 96 files, 1415 passed / 4 skipped, which is main's own count — no test changed state in either direction. The diff is two files, +5/-5: one line of package.json and the matching three-line entry plus declaration echo in package-lock.json. No other package moved in the lockfile, so the scope is exactly the one dependency the title names. The single subject is 33 characters and conventional. The installed @types/node resolves to 26.6.4, so the declaration and the tree agree. — Tree: 3b74a3ef57504f82263f12c047f2fb0b8c3499f7 — Head: e8a219e

Acceptance Criteria

• [met] The bump is confined to the one dependency the title names — Evidence: git diff origin/main...HEAD is package.json and package-lock.json only, and within the lockfile the hunks are the root devDependencies echo and the node_modules/@types/node entry. Nothing else resolved differently, which is the thing a grouped Dependabot pull request can quietly get wrong — proof: protections/the-major-plants-still-describe-this-tree > every plant's text is still in its subject, exactly once (green here) together with the measured two-file diff
• [met] The plant anchors survive the bump, on the real case rather than a planted one — Evidence: tests/protections/majors.ts anchors @types/node on "@types/node": "^26, the major alone. 26.6.3 → 26.6.4 leaves that substring intact, so both mutations still find their subject and the protections suite is green. fix(majors): anchor the @types/node plants on the major, not the patch #119 changed the anchor from the patch to the major and proved it against a control with a synthetic ^26.7.1; this pull request is the first scheduled patch bump to arrive since, and it passes. The claim fix(majors): anchor the @types/node plants on the major, not the patch #119 made has now met the event it was built for — proof: protections/the-major-plants-still-describe-this-tree > every plant's text is still in its subject, exactly once
• [met] Nothing the types describe regressed — Evidence: tsc --noEmit exits 0 and the full suite matches main at 1415 passed / 4 skipped with a database attached. A @types/node bump can only act through the compiler, and the compiler is the thing that ran clean — proof: npm run typecheck, plus vitest run with DATABASE_URL set

Findings

none

Not Checked

• Whether a @types/node minor bump within major 26 would behave the same. It must, by the same substring argument, but I measured the patch that is actually here and did not plant a minor.
• What the four skipped tests are. They are skipped on main at the same count, so this pull request did not change them, and I did not open them.
• The runtime Node major as opposed to the declared @types/node major. repo-config.test.ts says in its own comment that it reads declarations and names drift above the caret rather than catching it; this diff does not touch that boundary.
• Anything about the 1415 tests outside the compiler's reach. The gate ran them green; I did not reason about them individually.
• Whether @types/node 26.6.4 changes any type this repository does not use. The declaration is a caret range, so npm was already free to resolve here; the question this pull request raises is only whether the pinned floor moving breaks the tree, and it does not.

Routed

none

---

Generated by Claude Code