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 regressions)
✅ Have no breaking changes (patch-only bumps)
✅ npm audit reports 0 vulnerabilities before and after
Updated Dependencies
Package
Previous
Updated
Type
js-yaml
5.4.1
5.4.2
patch
@babel/core
^8.0.1
^8.0.6
patch
@babel/preset-env
^8.0.2
^8.0.6
patch
@commitlint/cli
^21.2.2
^21.2.3
patch
@commitlint/config-conventional
^21.2.2
^21.2.3
patch
babel-jest
^30.5.1
^30.5.2
patch
jest
^30.5.1
^30.5.2
patch
ts-jest
^29.4.12
^29.4.13
patch
markdownlint-cli2
^0.23.2
^0.23.3
patch
Security Fixes Included
None — npm audit reported 0 vulnerabilities both before and after these updates, and no open Dependabot alerts exist for this repository. This PR is a routine patch-level freshness update, not a CVE remediation.
Verification
npm run build (tsc) passes
npm test run: 386/395 test suites pass (9 pre-existing failures in src/enclave/mount-policy.test.ts reproduce identically on main without these changes — caused by the sandbox lacking a writable /var/tmp, unrelated to this update)
Larger available updates (e.g. commander 12→15, chalk 4→6, typescript 5→7, execa 5→10) were intentionally excluded as they are major version bumps that may include breaking changes and require dedicated review/testing.
@types/glob, @typescript-eslint/*, @types/node, and eslint were left unchanged: either already at "Wanted" or requiring a version bump beyond patch level.
js-yaml remains exact-pinned (no ^) per existing repository convention (it's also referenced via an overrides entry using $js-yaml).
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 2 domains
The following domains were blocked by the firewall during workflow execution:
msfeed25.pkgs.visualstudio.com
registry.npmjs.org
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 before and afterUpdated Dependencies
@babel/core@babel/preset-env@commitlint/cli@commitlint/config-conventionalSecurity Fixes Included
None —
npm auditreported 0 vulnerabilities both before and after these updates, and no open Dependabot alerts exist for this repository. This PR is a routine patch-level freshness update, not a CVE remediation.Verification
npm run build(tsc) passesnpm testrun: 386/395 test suites pass (9 pre-existing failures insrc/enclave/mount-policy.test.tsreproduce identically onmainwithout these changes — caused by the sandbox lacking a writable/var/tmp, unrelated to this update)npm audit --registry=https://registry.npmjs.org/→ 0 vulnerabilitiesNotes
commander12→15,chalk4→6,typescript5→7,execa5→10) were intentionally excluded as they are major version bumps that may include breaking changes and require dedicated review/testing.@types/glob,@typescript-eslint/*,@types/node, andeslintwere left unchanged: either already at "Wanted" or requiring a version bump beyond patch level.js-yamlremains exact-pinned (no^) per existing repository convention (it's also referenced via anoverridesentry using$js-yaml).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 2 domains
The following domains were blocked by the firewall during workflow execution:
msfeed25.pkgs.visualstudio.comregistry.npmjs.orgTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.