Bump @humanfs/node from 0.16.6 to 0.16.8

[dependabot]

Bumps @humanfs/node from 0.16.6 to 0.16.8.

Release notes

Sourced from @​humanfs/node's releases.

node: v0.16.8

0.16.8 (2026-04-17)

Bug Fixes

• Include type dependencies at runtime (956ce7a), closes #145

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​humanfs/core bumped from ^0.19.1 to ^0.19.2

node: v0.16.7

0.16.7 (2024-11-27)

Bug Fixes

• Add directory to package.json (f691b60)

Changelog

Sourced from @​humanfs/node's changelog.

0.16.8 (2026-04-17)

Bug Fixes

• Ensure symlinks are copied as symlinks in copy() and copyAll() (22bbaa44)
• Include type dependencies at runtime (956ce7a), closes #145

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​humanfs/core bumped from ^0.19.1 to ^0.19.2

0.16.7 (2024-11-27)

Bug Fixes

• Add directory to package.json (f691b60)

Commits

• e96070e chore: release main (#146)
• 22bbaa4 Merge commit from fork
• 956ce7a fix: Include type dependencies at runtime
• 257b7b5 chore: release main (#142)
• f691b60 fix: Add directory to package.json
• 7b81d9a chore(deps): Upgrading retry dependency in node package. (#140)
• See full diff in compare view

[bgentry]

🤖 Codex review: Approved after dependency security and compatibility review.

Upgrade

• @humanfs/node: 0.16.6 → 0.16.8
• Reviewed head: b8b9aacdd38b14ba700ad6e20af3517ed3ce7e2b

Security review

• This is a confirmed security update: 0.16.8 is the first version patched for GHSA-p498-v437-472g, which covers symlink traversal/file disclosure in copy() and copyAll(). River's exposure is limited because this is a dev-only transitive dependency through ESLint.
• The lockfile also moves @humanfs/core from 0.19.1 to 0.19.2, adds the types-only @humanfs/types@0.15.0, and reuses the existing top-level @humanwhocodes/retry@0.4.2 instead of nested 0.3.1.
• Exact npm tarball SHA-512 values match the lockfile and registry metadata. Packaged source matches canonical upstream commits, including the verified fix source.
• No new install hooks, bins, native/platform packages, non-registry URLs, integrity rewrites, downloaders, network clients, telemetry, credential access, or process execution were found.

Compatibility verification

• npm ci on Node 24.14.1 / npm 11.11.0 — passed; lockfile unchanged
• npm run lint — passed
• npm run test:once — passed (34 files, 233 tests)
• npm run build — passed
• Focused copy() / copyAll() symlink-preservation regression — passed
• Required JS, Go, release, and public Docker checks pass. The Pro Docker failure is an AWS OIDC authorization failure on the Dependabot run and occurs before any build step.

Residual risk

• npm provenance attestations are absent, though registry signatures, integrity values, and upstream source identities were verified.
• npm audit reports an unrelated pre-existing brace-expansion advisory; this PR does not change that package.

[bgentry]

@dependabot rebase

[bgentry]

🤖 Codex review: Approved after dependency security and compatibility review.

Upgrade

• @humanfs/node: 0.16.6 → 0.16.8
• Reviewed head: 2f35e77c680c3d0dbec07d166b56a6a1e4f251f9

Security review

• This is a confirmed security update: 0.16.8 is the first version patched for GHSA-p498-v437-472g, the symlink traversal/file-disclosure issue in copy() and copyAll(). River's exposure is limited because this is a dev-only transitive dependency through ESLint.
• The lockfile also moves @humanfs/core from 0.19.1 to 0.19.2, adds the type-only @humanfs/types@0.15.0, and reuses the existing top-level @humanwhocodes/retry@0.4.2 instead of nested 0.3.1.
• Exact npm tarball SHA-512 values match the lockfile and registry metadata. Packaged source matches canonical upstream commits, including the signed security-fix commit and its regression tests.
• No new install hooks, bins, native/platform packages, non-registry URLs, integrity rewrites, downloaders, telemetry, credential access, or process execution were found.
• Dependabot rebased the PR after the artifact review. git range-diff confirms the dependency patch is byte-for-byte identical, so the exact-version and integrity evidence is unchanged; only the combined repository tree required revalidation.

Compatibility verification

• npm ci --ignore-scripts on Node 24.14.1 / npm 11.11.0 — passed; lockfile unchanged
• npm ls @humanfs/node @humanfs/core @humanfs/types @humanwhocodes/retry — passed with the expected deduplicated graph
• npm run lint — passed
• npm run test:once — passed (34 files, 233 tests)
• npm run build — passed
• Required JS, Go, release, and public Docker checks pass on the rebased head. The Pro Docker failure is an AWS OIDC authorization failure on the Dependabot run and occurs before any build step.

Residual risk

• npm provenance attestations are absent, though registry signatures, integrity values, publisher continuity, gitHead, and upstream source identities were verified.
• npm audit reports an unrelated pre-existing brace-expansion advisory; this PR does not change that package.