mirror of
https://github.com/headroomlabs-ai/headroom.git
synced 2026-11-22 13:29:19 +08:00
fix(deps): patch brace-expansion in wrap E2E lockfile (#3873)
## Description The `npm audit (e2e/wrap/tools)` check fails on the transitive `brace-expansion@5.0.9` lockfile entry. Three high-severity denial-of-service advisories affect versions through 5.0.11. The parent dependency permits `^5.0.8`, so the patched 5.0.12 release resolves this without changing the direct CLI dependencies. ## Type of Change - [x] Bug fix (non-breaking change that fixes an issue) - [ ] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update - [ ] Performance improvement - [ ] Code refactoring (no functional changes) ## Changes Made - Updated only `e2e/wrap/tools/package-lock.json`: `brace-expansion` 5.0.9 -> 5.0.12 (version, registry URL and integrity). - Left `@openai/codex`, `openclaw`, application code, and all other lock entries unchanged. ## Testing - [ ] Unit tests pass (`pytest`) — not applicable to this lockfile-only dependency update. - [ ] Linting passes (`ruff check .`) — no Python files changed. - [ ] Type checking passes (`mypy headroom`) — no Python files changed. - [ ] New tests added for new functionality — no new functionality. - [x] Manual testing performed ### Test Output ```text $ cd e2e/wrap/tools && npm audit --package-lock-only --audit-level=low Before: 1 high severity vulnerability (brace-expansion 5.0.9) After: found 0 vulnerabilities $ npm ci --ignore-scripts --dry-run --no-audit --no-fund added 333 packages (dry run); brace-expansion 5.0.12 $ git diff --check (no errors) ``` The dry run emitted engine warnings because the local Node 25.9.0 is outside `openclaw`'s declared supported range; these warnings are unrelated to this lockfile update and did not fail the command. ## Real Behavior Proof - Environment: clean branch from `main` (`8ff46dc9`), npm 11.12.1, Node 25.9.0; no application or provider credentials needed. - Exact command / steps: From the repository root, run `cd e2e/wrap/tools && npm audit --package-lock-only --audit-level=low` on the base commit to reproduce the advisory. With this lockfile change, run the same command again; it reports zero vulnerabilities. Then run `npm ci --ignore-scripts --dry-run --no-audit --no-fund` to verify lockfile install consistency. - Observed result: baseline audit exited nonzero with GHSA-q2hr-2g5m-vwhr, GHSA-qhr7-859c-m2p7 and GHSA-6j4f-fj2g-mc7p. After the lock refresh the same command reports zero vulnerabilities. A dry-run `npm ci` accepts the updated lock. - Not tested: a full Docker wrap E2E, which does not change behavior under this dependency-only patch. ## Runtime Rollout Safety - Rollout-managed feature(s): None. This dependency is used by the Docker wrap E2E harness, not the Python runtime. - Minimum rollout channel: Normal dependency update. - Stable/default behavior changed: No application behavior change. - Kill switch / disable path: Not applicable. - Unsafe override required: No. - Qualification impact: Clears the audit gate only. - Rollback path: Revert the lockfile update. ## Review Readiness - [x] I have performed a self-review - [x] This PR is ready for human review ## Checklist - [x] My code follows the project's style guidelines - [x] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas — no source code changed. - [ ] I have made corresponding changes to the documentation — not applicable. - [x] My changes generate no new warnings attributable to this patch - [ ] I have added tests that prove my fix is effective or that my feature works — audit gate is the regression check. - [x] New and existing checks relevant to this lockfile pass locally - [x] I did **not** edit `CHANGELOG.md` — it is generated by release-please from my Conventional Commit PR title ## Screenshots (if applicable) Not applicable. ## Additional Notes This is independent of the Python changes in #3871 and #3872; both currently inherit the same repository-wide audit failure.
This commit is contained in:
Generated
+3
-3
@@ -1546,9 +1546,9 @@
|
||||
"license": "MIT"
|
||||
},
|
||||
"node_modules/brace-expansion": {
|
||||
"version": "5.0.9",
|
||||
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-5.0.9.tgz",
|
||||
"integrity": "sha512-ScQ4IuvIEF1TMlP7Zt+vjJ//9zlPb2SDcxWxM3bk8s6t6GGdJ7KO1dCcTidOPJKePW30LE/2cT7wCyPho9/Wxg==",
|
||||
"version": "5.0.12",
|
||||
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-5.0.12.tgz",
|
||||
"integrity": "sha512-YovQ3rzhaLMIrDjNDMkNS01tea93qhEhG5xy8f6+R0l+dw3Ki+5sCoIoI942iuLZTHWogWktgwVDhU09iNEimQ==",
|
||||
"license": "MIT",
|
||||
"dependencies": {
|
||||
"balanced-match": "^4.0.2"
|
||||
|
||||
Reference in New Issue
Block a user