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

Dependency Security Monitor · issue · closed

Filter2mode:review mode:live
All recorded Export JSON
github-actions[bot]

published Aug 8, 2026, 3:12 AM · updated Aug 8, 2026, 6:40 PM

Automated Safe Dependency Updates

This PR contains safe patch-level dependency updates verified to pass the test suite and introduce no breaking changes.

Updated Dependencies

Package Previous Updated Type
eslint 10.8.0 10.8.1 patch
globals 17.8.0 17.9.0 patch
js-yaml 5.2.2 5.2.3 patch
@typescript-eslint/eslint-plugin 8.65.0 8.66.0 patch
@typescript-eslint/parser 8.65.0 8.66.0 patch
typescript-eslint 8.65.0 8.66.0 patch

Security Fixes Included

None — npm audit reported 0 vulnerabilities before and after this change. Dependabot alerts could not be queried (token lacks security_events/Dependabot read scope; 403 response), so no Dependabot-sourced CVEs are addressed here.

Verification

  • npm audit — 0 vulnerabilities
  • npm run build (tsc) — succeeds
  • npm test — 280/283 suites pass, 4494/4508 tests pass. The 3 failing suites (src/enclave/mount-policy.test.ts) fail identically on the pre-update baseline (verified via git stash) because /var/tmp is unavailable in this sandbox — unrelated to these dependency bumps.
  • Docker build verification — not performed (out of scope for this npm-only run)

Notes

Larger available upgrades (e.g. chalk@6, commander@15, execa@10, typescript@7, @babel/core@8) are major version bumps and were intentionally excluded as unsafe for an automated patch-only update; consider tracking them separately for manual review.


Generated by Dependency Security Monitor Workflow


Warning

Protected Files — Push Permission Denied

This was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.

Protected files
  • package-lock.json
  • package.json

The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission.

Create the pull request manually
# Download the patch from the workflow run
gh run download 31236493251 -n agent -D /tmp/agent-31236493251

# Create a new branch
git checkout -b deps/safe-patch-updates-20260808-add940c4f63d1675 main

# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-31236493251/aw-deps-safe-patch-updates-20260808.patch

# Push the branch and create the pull request
git push origin deps/safe-patch-updates-20260808-add940c4f63d1675
gh pr create --title '[Deps] Safe dependency updates (2026-08-08)' --base main --head deps/safe-patch-updates-20260808-add940c4f63d1675 --repo github/gh-aw-firewall

Generated by Dependency Security Monitor · auto · 29.8 AIC · ⊞ 12.7K ·