You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR contains safe patch-level dependency updates that have been verified to:
✅ Pass the full test suite (no new failures vs. base branch)
✅ Have no breaking changes (patch-level semver bumps only)
✅ npm audit reports 0 vulnerabilities (no CVEs to address)
Updated Dependencies
Package
Previous
Updated
Type
js-yaml (prod)
5.4.1
5.4.2
patch
@eslint/compat (dev)
2.1.0
2.1.1
patch
@types/node (dev)
25.9.5
25.9.6
patch
Security Fixes Included
None. npm audit --registry https://registry.npmjs.org reported 0 vulnerabilities (critical/high/moderate/low) at the time of this run, and no Dependabot alerts are currently open for this repository.
Verification
npm run build (tsc) succeeds
Full test suite run: 5825/5858 tests pass on both the base branch and this branch. The 33 failing tests (7 suites: enclave/mount-policy, enclave/github-gateway, enclave/dynamic-delegation*, docker-manager-diagnostics, enclave/manager) fail identically before and after these updates — root cause is /var/tmp not being creatable in this sandbox environment (pre-existing environment limitation, unrelated to dependency versions).
No breaking changes detected (all bumps are patch-level per semver)
Notes
Other outdated packages (chalk, commander, execa, typescript, @babel/*, jest, etc.) have available updates but are minor/major version bumps requiring more careful review and were intentionally excluded from this conservative, patch-only update batch.
js-yaml in dependencies was previously exact-pinned (no ^); this update preserves that exact pinning at the new patch version.
Generated by Dependency Security Monitor Workflow
Note
Protected files
This patch modifies protected files, which may affect project dependencies, CI/CD pipelines, or agent behaviour.
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 1 domain
The following domain was blocked by the firewall during workflow execution:
msfeed25.pkgs.visualstudio.com
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
Tip
Your pull request is ready to create! 🎉 ✅
Everything is OK—the changes have been pushed to a branch. Please review the protected files, then create the pull request when you are ready.
Create the pull request
The original pull request description is below.
Automated Safe Dependency Updates
This PR contains safe patch-level dependency updates that have been verified to:
npm auditreports 0 vulnerabilities (no CVEs to address)Updated Dependencies
@eslint/compat(dev)@types/node(dev)Security Fixes Included
None.
npm audit --registry https://registry.npmjs.orgreported 0 vulnerabilities (critical/high/moderate/low) at the time of this run, and no Dependabot alerts are currently open for this repository.Verification
npm run build(tsc) succeedsenclave/mount-policy,enclave/github-gateway,enclave/dynamic-delegation*,docker-manager-diagnostics,enclave/manager) fail identically before and after these updates — root cause is/var/tmpnot being creatable in this sandbox environment (pre-existing environment limitation, unrelated to dependency versions).Notes
chalk,commander,execa,typescript,@babel/*,jest, etc.) have available updates but are minor/major version bumps requiring more careful review and were intentionally excluded from this conservative, patch-only update batch.js-yamlindependencieswas previously exact-pinned (no^); this update preserves that exact pinning at the new patch version.Generated by Dependency Security Monitor Workflow
Note
Protected files
This patch modifies protected files, which may affect project dependencies, CI/CD pipelines, or agent behaviour.
Protected files
package-lock.jsonpackage.jsonTo route changes like this to a review issue instead of blocking, configure
protected-files: fallback-to-issuein your workflow configuration.Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
msfeed25.pkgs.visualstudio.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.