Skip to content

chore(deps-dev): bump @types/node from 26.1.1 to 26.2.0 - #33

Merged
edycutjong merged 1 commit into
mainfrom
dependabot/npm_and_yarn/types/node-26.1.2
Aug 12, 2026
Merged

chore(deps-dev): bump @types/node from 26.1.1 to 26.2.0#33
edycutjong merged 1 commit into
mainfrom
dependabot/npm_and_yarn/types/node-26.1.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 31, 2026

Copy link
Copy Markdown
Contributor

Bumps @types/node from 26.1.1 to 26.2.0.

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 31, 2026
@edycutjong

Copy link
Copy Markdown
Owner

@dependabot rebase

@dependabot @github

dependabot Bot commented on behalf of github Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

Dependabot can't parse your pnpm-lock.yaml. Because of this, Dependabot cannot update this pull request.

edycutjong added a commit that referenced this pull request Aug 12, 2026
…ories

pnpm-lock.yaml had '@napi-rs/wasm-runtime@1.2.2' as a top-level key four
times, so 'pnpm install --frozen-lockfile' failed with
ERR_PNPM_BROKEN_LOCKFILE and every CI stage died at install (red since
2026-08-07). Dependabot hit the same wall — 'pnpm-lock.yaml not
parseable' — so it could neither raise nor fix alerts here, and the
security tab showed only 2 of the 6 advisories actually in the tree.

Regenerated the lockfile and raised the pins the audit then exposed:

  js-yaml (3.x)    -> 3.15.1
  js-yaml (4.x)    -> 4.3.1
  ip-address       -> 10.5.0   (>=10.3.1 required, was hidden)
  brace-expansion  -> 5.0.9    (>=5.0.9 required, was hidden)
  nanoid           -> 3.3.18   (>=3.3.17 required, was hidden)
  body-parser      -> 2.3.0    (>=1.20.6 required, was hidden)

postcss was pinned exactly at 8.5.23, which held nanoid at a vulnerable
3.3.16; floating it to ^8.5.23 plus a nanoid@3 override fixes both.

Also folds in the three stuck Dependabot PRs (#40 #33 #31), which could
never merge against the broken lockfile: next 16.2.11 -> 16.3.0,
react-dom 19.2.7 -> 19.2.8, @types/node floats to 26.1.2.

Verified: pnpm install --frozen-lockfile succeeds, pnpm audit reports no
known vulnerabilities, typecheck clean, 183/183 tests, next build green
from a cold cache.
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 26.1.1 to 26.2.0.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-version: 26.1.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps-dev): bump @types/node from 26.1.1 to 26.1.2 chore(deps-dev): bump @types/node from 26.1.1 to 26.2.0 Aug 12, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/types/node-26.1.2 branch from 0c8ed1b to 21522c4 Compare August 12, 2026 10:09
@edycutjong
edycutjong merged commit 96fe84b into main Aug 12, 2026
10 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/types/node-26.1.2 branch August 12, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant