@devries-cameron20 / composio-1 / commits / 07160d14f
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

feat(toolchain): introduce mise.toml as single source of truth (#3492)

## Summary This PR starts Phase 1 of PLEN-1368 by adding `mise.toml` as the repo-owned source for the primary toolchain versions: - Node `20.20.2` - Bun `1.3.10` - Deno `2.6.7` - Python `3.12` - uv `0.8.19` It also keeps pnpm corepack-driven through `package.json#packageManager`, adds `devEngines` for Node/pnpm visibility, documents the new `mise install && corepack enable && pnpm install` bootstrap path, ignores `.mise.local.toml`, and fixes stale release-doc prerequisites. ## Why The repo already has real toolchain drift, not just duplicated version strings. The internal release docs had stale Node/Bun/pnpm versions, Deno is repeated across workflows, Dockerfiles, docs, and e2e helpers, and Python local setup still has a separate `3.11` venv path while the repo pins `3.12`. A composite-action cleanup would improve CI, but it would not solve local development. `mise.toml` gives us one file that declares the versions and lets contributors install or switch them with one command. That is the main value proposition here: make the repo declare its own toolchain, then let CI consume the same declaration in the next phase. ## Rollout This is deliberately additive. It does not remove `.nvmrc`, `.bun-version`, `.python-version`, or `.dvmrc`, and it does not change CI behavior yet. Contributors who do not use mise can keep working as before; contributors who do use mise get managed Node/Bun/Deno/Python/uv immediately. Phase 2 can migrate the existing composite actions to `jdx/mise-action@v4`. Phase 3 can remove the legacy version files and add the lockfile once the transition is complete. ## Out of Scope - Migrating CI to `jdx/mise-action@v4` - Removing legacy version files - Adding `mise.lock` - Updating nested TS package/example `packageManager` fields that still say `pnpm@10.28.0`; that is pre-existing metadata drift and should be handled separately to avoid broadening Phase 1 ## Verification - `git diff --check origin/next...HEAD` - `mise install && mise current` - `pnpm --version` -> `10.28.2` - `pnpm dlx prettier@3.8.1 --check package.json` Refs: PLEN-1368

Alberto Schiabel committed Jun 5, 2026 at 10:50 UTC 07160d14fa0411088d215bbbd82bae8bd499609c
6 files changed +64 -9
.gitignore
+3
@@ -62,3 +62,6 @@ test/e2e/*/node_modules
62
63 # Agent memory
64 .agent_cache
65 +
66 +# mise (per-dev overrides)
67 +.mise.local.toml
AGENTS.md
+11 -4
@@ -26,6 +26,8 @@ pnpm test # Run tests
26
27 ### Package Management
28 ```bash
29 +mise install # Install Node, Bun, Deno, Python, uv (one-time; needs mise — https://mise.jdx.dev/installing-mise.html)
30 +corepack enable # Activate pnpm from package.json#packageManager
31 pnpm install # Install dependencies
32 pnpm check:peer-deps # Check peer dependencies
33 pnpm update:peer-deps # Update peer dependencies
@@ -195,10 +197,15 @@ make build # Build packages
197
198 ### When Updating GitHub Actions
199
198 -Update the "Prerequisites" section in `ts/docs/internal/release.md` with current tool versions:
200 +Toolchain versions are coalesced in `mise.toml`. To check the current values:
201
200 -- **Node.js**: `cat .nvmrc`
201 -- **Bun**: `cat .bun-version`
202 -- **pnpm**: `cat package.json | jq -r .packageManager | cut -d'@' -f2`
202 +- **Node.js**: `mise current node`
203 +- **Bun**: `mise current bun`
204 +- **Deno**: `mise current deno`
205 +- **Python**: `mise current python`
206 +- **uv**: `mise current uv`
207 +- **pnpm**: `node -p "require('./package.json').packageManager"`
208 +
209 +To bump, edit `mise.toml` (or `package.json#packageManager` for pnpm). The "Prerequisites" section in `ts/docs/internal/release.md` references `mise.toml` so it stays current automatically.
210
211 This monorepo uses pnpm workspaces and Turbo for efficient builds and development.
CLAUDE.md
+5 -2
@@ -29,6 +29,8 @@ composio/
29 ## TypeScript Commands
30
31 ```bash
32 +mise install # Installs Node, Bun, Deno, Python, uv from mise.toml (one-time per machine)
33 +corepack enable # Activates pnpm pinned in package.json#packageManager
34 pnpm install # First-time setup. Use BYPASS_BUN_VERSION_CHECK=1 if .bun-version mismatch
35 pnpm build # Build all packages (Turbo)
36 pnpm build:packages # TS packages only
@@ -45,7 +47,7 @@ pnpm create:provider <name> [--agentic]
47 pnpm create:example <name>
48 ```
49
48 -Pinned tool versions: Node `.nvmrc` (20.20.2), Bun `.bun-version` (1.3.10), pnpm via `packageManager` in `package.json`. CI sets `BYPASS_BUN_VERSION_CHECK=1`; local sandboxes often need it too.
50 +Toolchain versions are pinned in `mise.toml` (Node, Bun, Deno, Python, uv) and `package.json#packageManager` (pnpm via corepack). Install mise once with `brew install mise` (macOS), `winget install jdx.mise` (Windows), or `curl https://mise.run | sh` (any), then activate it in your shell — see https://mise.jdx.dev/installing-mise.html. Legacy `.nvmrc` / `.bun-version` / `.python-version` are still read during the transition. CI sets `BYPASS_BUN_VERSION_CHECK=1`; local sandboxes often need it too.
51
52 ## Python Commands
53
@@ -87,7 +89,8 @@ COMPOSIO_DISABLE_TELEMETRY # "true" to disable
89 - Core Composio class: `ts/packages/core/src/composio.ts`
90 - Types: `ts/packages/core/src/types/`, errors: `ts/packages/core/src/errors/`
91 - Build configs: `turbo.jsonc`, `tsconfig.base.json`, `tsdown.config.base.ts`
90 -- CI release docs to update when bumping toolchain: `ts/docs/internal/release.md` (Node/Bun/pnpm versions)
92 +- Toolchain pins: `mise.toml` (Node, Bun, Deno, Python, uv), `package.json#packageManager` (pnpm), `.dvmrc` (Deno; mirrors mise.toml for `denoland/setup-deno` and `_utils/src/config.ts`)
93 +- CI release docs to update when bumping toolchain: `ts/docs/internal/release.md`
94 - Python config: `python/Makefile`, `python/noxfile.py`, `python/config/{pytest.ini,ruff.toml}`
95
96 ## See Also
mise.toml new
+30
@@ -0,0 +1,30 @@
1 +# Single source of truth for Node, Bun, Deno, Python, and uv versions.
2 +#
3 +# Local dev: `mise install` (after `brew install mise` / `winget install jdx.mise` / `curl https://mise.run | sh`)
4 +# CI: driven by `jdx/mise-action@v4` in the composite actions under `.github/actions/`
5 +#
6 +# pnpm is intentionally NOT pinned here. Pattern A (corepack-driven) is in effect:
7 +# the version comes from `packageManager` in `package.json` and corepack shims it.
8 +# See https://github.com/jdx/mise/discussions/7622 for why pinning pnpm in [tools] can shadow corepack.
9 +
10 +min_version = "2026.1.0"
11 +
12 +[tools]
13 +node = "20.20.2"
14 +bun = "1.3.10"
15 +deno = "2.6.7"
16 +python = "3.12"
17 +uv = "0.8.19"
18 +
19 +[env]
20 +_.path = ["{{config_root}}/node_modules/.bin"]
21 +
22 +[settings]
23 +# Read .nvmrc / .python-version / .bun-version during the transition window.
24 +# Removed in Phase 3 once the legacy files are deleted.
25 +idiomatic_version_file_enable_tools = ["node", "python", "bun"]
26 +
27 +# uv integration: mise installs Python, uv owns the venv.
28 +# "source" activates an existing .venv when entering the repo;
29 +# use "create|source" if you want mise to also create the venv automatically.
30 +python.uv_venv_auto = "source"
package.json
+12
@@ -52,6 +52,18 @@
52 "clean:workspace": "pnpm turbo clean"
53 },
54 "packageManager": "pnpm@10.28.2",
55 + "devEngines": {
56 + "runtime": {
57 + "name": "node",
58 + "version": "20.20.2",
59 + "onFail": "warn"
60 + },
61 + "packageManager": {
62 + "name": "pnpm",
63 + "version": "10.28.2",
64 + "onFail": "warn"
65 + }
66 + },
67 "devDependencies": {
68 "@arethetypeswrong/cli": "catalog:",
69 "@changesets/cli": "^2.29.8",
ts/docs/internal/release.md
+3 -3
@@ -79,9 +79,9 @@ The manual release process is available for cases where direct control over the
79
80 ### Prerequisites
81
82 -- Node.js (version: `20.19.0`)
83 -- Bun (version: `1.3.6`)
84 -- pnpm (version: `10.28.0`)
82 +- Node.js (version: `20.20.2`)
83 +- Bun (version: `1.3.10`)
84 +- pnpm (version: `10.28.2`)
85 - Access to npm registry
86 - Write access to the repository
87