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 a safe patch-level dependency update identified by the Dependency Security Monitor workflow.
Vulnerability Assessment
npm audit (run against the public npm registry): 0 vulnerabilities found across 924 dependencies (prod 31, dev 894, optional 68).
Dependabot alerts: No open alerts of any severity for this repository at time of run.
Existing security issues: Searched for open issues labeled security/dependencies — none found.
Existing dependency-update PRs: Searched for open PRs — none found, so this PR was created fresh.
Updated Dependencies
Package
Previous
Updated
Type
js-yaml
5.4.1
5.4.2
patch
Security Fixes Included
None — this update was not driven by a specific CVE. It is a routine safe patch-level bump identified via npm outdated (checked against the public npm registry, since the repository's configured registry endpoint is not reachable through the firewall in this environment).
Notes
Other outdated packages (@babel/core, @babel/preset-env, @types/node, @typescript-eslint/*, eslint, chalk, commander, execa, typescript, jest, babel-jest) were reviewed but not updated in this PR because they involve minor/major version jumps, not safe patch-level bumps, and are out of scope for this conservative automated update.
package-lock.json was regenerated via npm install to reflect the bump.
Verification
npm run build succeeds (TypeScript compiles cleanly)
Full unit test suite run: 5954/5988 tests pass. The same 34 failures occur identically on main without this change (all in src/enclave/*.test.ts, caused by the sandbox lacking a writable /var/tmp directory) — confirmed pre-existing and unrelated to this update.
No breaking changes expected for a patch-level semver bump
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 Update
This PR contains a safe patch-level dependency update identified by the Dependency Security Monitor workflow.
Vulnerability Assessment
npm audit(run against the public npm registry): 0 vulnerabilities found across 924 dependencies (prod 31, dev 894, optional 68).security/dependencies— none found.Updated Dependencies
js-yamlSecurity Fixes Included
None — this update was not driven by a specific CVE. It is a routine safe patch-level bump identified via
npm outdated(checked against the public npm registry, since the repository's configured registry endpoint is not reachable through the firewall in this environment).Notes
@babel/core,@babel/preset-env,@types/node,@typescript-eslint/*,eslint,chalk,commander,execa,typescript,jest,babel-jest) were reviewed but not updated in this PR because they involve minor/major version jumps, not safe patch-level bumps, and are out of scope for this conservative automated update.package-lock.jsonwas regenerated vianpm installto reflect the bump.Verification
npm run buildsucceeds (TypeScript compiles cleanly)mainwithout this change (all insrc/enclave/*.test.ts, caused by the sandbox lacking a writable/var/tmpdirectory) — confirmed pre-existing and unrelated to this update.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.