Skip to content

chore(deps): refresh transitive dependencies and stabilize monitor tests - #26

Merged
steipete merged 1 commit into
mainfrom
chore/deps-refresh-20260830
Aug 31, 2026
Merged

steipete merged 1 commit into
mainfrom
chore/deps-refresh-20260830

Conversation

@steipete

@steipete steipete commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Refresh the four outdated transitive dependencies within their existing parent ranges, and fix a monitor-test readiness race exposed by the baseline test run. The POSIX fixture now writes its child PID before emitting ready; the startup-error assertion waits for the warning instead of sleeping for 100 ms. All assertions remain intact.

Dependency Before After
express-rate-limit 8.6.2 8.7.0
ip-address 10.5.0 10.7.0
qs 6.15.3 6.16.0
zod 4.4.3 4.5.4

Regenerated package-lock.json with npx --yes npm@11.19.1 update. All direct dependencies and all five pinned GitHub Actions are already current; no dependencies were added. No direct-dependency major update is outstanding. Transitive releases outside their parent packages' declared ranges remain upstream-owned; no overrides were introduced.

Retained npm 11.19.1: npm 12 requires Node ^22.22.2, ^24.15.0, or >=26, which excludes the documented and tested Node 22.19 minimum. Recommendation: keep npm 11 until the minimum-supported-Node policy changes.

Compatibility

The change affects dependency resolution and test synchronization only. No Babelfish command, manifest, generated name, install location, trust permission, or compatibility semantic changes. No README or changelog update is needed for this maintenance-only change.

Verification

Codex autoreview returned scoped-clean with no accepted/actionable findings at the skill's default P0 threshold. git diff --check passed.

Full clean install, build, tests, package check, and live proof were run sequentially with this exact command:

npx --yes --package=node@22.19.0 --package=npm@11.19.1 --call 'node --version && npm --version && npm ci && npm run check && npm run pack:check && node test/low-memory/e2e.mjs'

Actual output excerpts:

v26.8.1
11.19.1
added 145 packages, and audited 146 packages in 21s
found 0 vulnerabilities

> node scripts/clean-dist.mjs && tsc -p tsconfig.json && node scripts/build.mjs

Test Files  9 passed (9)
     Tests  63 passed (63)

Package contains 43 files (471863 bytes unpacked).
{"installed":{"hermes":1,"claude-code":1,"codex":1},"generatedTools":3,"mcpTools":8}

The npm wrapper selected the host Node 26.8.1 despite the Node package request; these are Node 26 results, with Python 3.14.7. The unchanged CI matrix verifies Node 22.19 on Linux/macOS/Windows and Node 24 on Linux.

The integration command node test/low-memory/e2e.mjs launches the actually built dist/bin.js in a temporary runtime, installs real local Git fixture repositories for Hermes, Claude Code, and Codex, lists them, validates generated tools, connects an MCP client over stdio, invokes simple_echo, and uninstalls all three. It uses isolated state and removes its temporary runtime. This local invocation proves the lifecycle and MCP path; it does not claim Docker memory limits.

CI reasoning

The orchestrator reported NORUNS, but the exact current main commit already has a successful four-platform/runtime build-test CI run. CodeQL's latest scheduled scan also passed. No default-branch CI failure or production change was needed.

CI is the build/test/package gate. Low-memory is the Docker resource-constrained test/integration gate triggered on PRs and manually. CodeQL is security analysis on PRs, pushes, and a weekly schedule. ClawSweeper Dispatch is operational event dispatch, not build/test evidence.

The first local baseline run exposed the PID-file race fixed here. An overlapping local test run subsequently timed out in three Git fixture tests; the final serial gate passed all 63 tests with the existing timeouts and assertions. PR validation passed on commit 0a2f69a: all four CI jobs, CodeQL, and the Docker constrained-memory matrix. No CI reruns or assertion changes were needed. This PR remains open for maintainer review and has not been merged.

@clawsweeper

clawsweeper Bot commented Aug 31, 2026

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

@steipete
steipete merged commit 186e295 into main Aug 31, 2026
10 checks passed
@steipete
steipete deleted the chore/deps-refresh-20260830 branch August 31, 2026 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant