[Deps] Safe dependency updates (2026-08-25)

Automated Safe Dependency Updates

This PR contains safe patch-level dependency updates verified to pass build, lint, and (pre-existing-failure-adjusted) tests.

Updated Dependencies

Package	Previous	Updated	Type
eslint	10.9.0	10.9.1	patch
`@typescript-eslint/eslint-plugin`	8.67.0	8.68.0	patch
`@typescript-eslint/parser`	8.67.0	8.68.0	patch
typescript-eslint	8.67.0	8.68.0	patch

Security Fixes Included

None — npm audit reported 0 vulnerabilities at time of this run, and Dependabot alerts were not accessible with the current token (403, missing security_events scope). No HIGH/CRITICAL CVEs were found requiring a dedicated security issue.

Verification

npm run build passes
npm run lint passes (0 errors, pre-existing warnings only, unrelated to these packages)
npm test — 5146/5161 tests pass; the 15 failures are in src/enclave/mount-policy.test.ts and src/enclave/* and are caused by the sandbox missing /var/tmp (ENOENT: no such file or directory, mkdtemp '/var/tmp/...'), confirmed pre-existing by reproducing on main before applying these updates (identical failures on stashed/original package.json)

Notes

Larger available updates (chalk v6, commander v15, execa v10, typescript v7, @babel/* v8) are major version bumps and were intentionally skipped as not "safe" patch-level updates; they would need separate review for breaking changes.
No open [Deps]-prefixed PR existed prior to this run, so a new PR was created.

Generated by Dependency Security Monitor Workflow

Warning

Protected Files

This was originally intended as a pull request, but the patch modifies protected files. These files may affect project dependencies, CI/CD pipelines, or agent behaviour. Please review the changes carefully before creating the pull request.

Click here to create the pull request once you have reviewed the changes

Protected files

package-lock.json

package.json

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Warning

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

msfeed2.pkgs.visualstudio.com
msfeed25.pkgs.visualstudio.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "msfeed2.pkgs.visualstudio.com"
    - "msfeed25.pkgs.visualstudio.com"

See Network Configuration for more information.

Generated by Dependency Security Monitor · auto · 30.7 AIC · ⊞ 13.2K · ◷