Bump @humanfs/node from 0.16.6 to 0.16.8 - #681
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [@humanfs/node](https://github.com/humanwhocodes/humanfs/tree/HEAD/packages/node) from 0.16.6 to 0.16.8. - [Release notes](https://github.com/humanwhocodes/humanfs/releases) - [Changelog](https://github.com/humanwhocodes/humanfs/blob/main/packages/node/CHANGELOG.md) - [Commits](https://github.com/humanwhocodes/humanfs/commits/node-v0.16.8/packages/node) --- updated-dependencies: - dependency-name: "@humanfs/node" dependency-version: 0.16.8 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
bgentry
approved these changes
Sep 3, 2026
bgentry
left a comment
bgentry
left a comment
Contributor
There was a problem hiding this comment.
🤖 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.8is the first version patched for GHSA-p498-v437-472g, which covers symlink traversal/file disclosure incopy()andcopyAll(). River's exposure is limited because this is a dev-only transitive dependency through ESLint. - The lockfile also moves
@humanfs/corefrom0.19.1to0.19.2, adds the types-only@humanfs/types@0.15.0, and reuses the existing top-level@humanwhocodes/retry@0.4.2instead of nested0.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 cion Node24.14.1/ npm11.11.0— passed; lockfile unchangednpm run lint— passednpm 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 auditreports an unrelated pre-existingbrace-expansionadvisory; this PR does not change that package.
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
1 participant
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.
Bumps @humanfs/node from 0.16.6 to 0.16.8.
Release notes
Sourced from @humanfs/node's releases.
Changelog
Sourced from @humanfs/node's changelog.
Commits
e96070echore: release main (#146)22bbaa4Merge commit from fork956ce7afix: Include type dependencies at runtime257b7b5chore: release main (#142)f691b60fix: Add directory to package.json7b81d9achore(deps): Upgrading retry dependency in node package. (#140)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.