Repository navigation
chore(deps): refresh transitive dependencies and stabilize monitor tests - #26
Merged
Merged
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.Regenerated
package-lock.jsonwithnpx --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-cleanwith no accepted/actionable findings at the skill's default P0 threshold.git diff --checkpassed.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:
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.mjslaunches the actually builtdist/bin.jsin 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, invokessimple_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.CIis the build/test/package gate.Low-memoryis the Docker resource-constrained test/integration gate triggered on PRs and manually.CodeQLis security analysis on PRs, pushes, and a weekly schedule.ClawSweeper Dispatchis 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.