Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
chore(toolchain): patch Node.js to the Oct 2026 security release (#5048)
## Summary Patch Node.js to the 20–21 Oct 2026 security release across our repos. That release fixes 10 CVEs, 4 of them high: a Brotli decoder RCE (CVE-2026-111497) and two TLS certificate-verification bypasses. The patched lines are 22.23.4, 24.22.1 and 26.12.1. ## Changes **Repo toolchain (local dev, CI, Docker E2E CLI image)** - `mise.toml`, `mise.lock`: Node `24.17.0` → `24.22.1`. The lockfile URLs and checksums come from the nodejs.org `SHASUMS256.txt`. - `package.json` `devEngines.runtime.version`: `>=24.17.0 <25` → `>=24.22.1 <25`. This only warns. **E2E runtime matrix** - `toolchain-versions.json`: `node` goes from `22.22.3, 24.17.0, 25.9.0` to `22.23.4, 24.22.1, 26.12.1`, and `nodeDigests` is updated to the matching `node:<v>-slim` multi-arch index digests, following the existing convention: - 22.23.4 `sha256:de170b39439eb0e5a3444ad7d60b015614a381e10fecae2e30ec9e735122f38d` - 24.22.1 `sha256:55fb5f5a527ea2c5c4a95f963e48ef90aa38c7b346054fdc8ee9957a2b55d205` - 26.12.1 `sha256:36793bcbb160a6a16cede1e62b93f84e26b78a972a8a4c0b879c1c12f22761ec` - Node 25 is end-of-life and gets no patch, so the "current" slot in the matrix now runs 26.12.1. - The `versions.node` arrays in every `ts/e2e-tests/runtimes/node/*/e2e.test.ts` were updated to match, along with the e2e READMEs, `_utils` JSDoc examples and the `Dockerfile.node`/`Dockerfile.cli` usage comments. **Unchanged on purpose** - Published `engines.node` floors stay as they are: `>=22.22.3`, and `>=24.17.0` for `@composio/typesafe`. The docs, context7 expectations and `test/release-workflow.test.ts` that mirror those floors are also unchanged. Raising a floor affects users, needs changesets and is a maintainer call. The E2E matrix now tests 22.23.4 rather than the exact 22.22.3 floor. - `docs/.node-version` (`24`) is a floating major. The docs deploy picks up the patched build on its next build. ## Follow-up (needs workflows permission) The GitHub App token used for this branch can't update workflow files, so this edit was dropped from the commit: - `.github/workflows/ts.release.yml:47`: `node-version: '24.17.0'` → `node-version: '24.22.1'` Until that lands, the release job keeps running on 24.17.0, while the rest of CI uses 24.22.1 from `mise.lock`. ## Validation - Pulled each pinned digest from the ECR Public mirror (`public.ecr.aws/docker/library/node:<v>-slim@<digest>`), which the E2E Dockerfiles use, and ran `node --version`. The results were v22.23.4, v24.22.1 and v26.12.1. The digests also match Docker Hub's tag API. - A full `Dockerfile.node` toolchain build got through the pinned `FROM` and apt steps and then ran out of local disk during `mise install`. That stage is left to CI. - `node ts/scripts/validate-agent-skills.mjs`, `test-skill-routing.mjs` and `validate-changesets.mjs` passed. - `tsc --noEmit -p ts/e2e-tests/_utils` passed. - `prettier --check` on the touched files reported only two warnings, and both were already there before this change. No changeset is included because no published package changes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
No changes.