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(cli): release CLI 0.5.0 (#5001)
This PR: - releases the CLI's Unreleased changes as **0.5.0**, a minor release: `composio execute` exits 1 on a failed execution (#5002), five commands exit 1 on invalid input (#4998), and `orgs switch` exits 1 on an empty stored key (#5029), where they used to exit 0 - splits `ts/packages/cli/CHANGELOG.md` into Minor Changes (the three exit-code changes, with a breaking note) and Patch Changes (#4754's Dashboard execution, #5000's stored-login backend, #5003's `--account` usage error, #5029's `connected-accounts list` shape check, the `composio link` wording, the rc.19 client) - adds `docs/content/changelog/10-21-26-cli-release.mdx` with a Breaking changes section - no Changeset, and the CLI `package.json` is unchanged: the version comes from the beta that gets promoted ## Context ### Releasing 0.5.0 Automatic betas from `next` are numbered `0.4.6-beta.N`, so they can't become 0.5.0. Per `.agents/skills/cli-release/references/release-workflow.md`, an intentional minor needs an explicitly versioned beta: 1. Merge this PR. It only touches the changelogs, so the beta can also be built before it merges; the binary is the same. 2. Dispatch `gh workflow run build-cli-binaries.yml --repo ComposioHQ/composio --ref next --raw-field action=build-beta --raw-field version=0.5.0`, and watch it through the installation tests. 3. Optionally re-run the upgrade check below against the new `@composio/cli@0.5.0-beta.N`. 4. Confirm that exact tag and dispatch `promote-stable` at it. The latest stable is 0.4.5, so `@composio/cli@0.5.0` is free. Merging this PR runs the docs changelog notification workflows for the new `.mdx`. ### Upgrade check Beta: `@composio/cli@0.4.6-beta.475`, target commit `09e2fb7faa41c51fcd364ee01e0aaf6719a62896` (#4754), published 2026-10-20T15:39:35Z. All six assets are `uploaded`, and [Build CLI Binaries run 39449485448](https://github.com/ComposioHQ/composio/actions/runs/39449485448) passed, including the installation tests. Each old version ran from its released `composio-darwin-aarch64.zip` (checksum matched the release's `checksums.txt`), unpacked into `$HOME/.composio` of a fresh temporary `HOME`, with telemetry off. | Old version | Upgrade command | Upgrade | `composio --version` | `composio run 'console.log(1)'` | Script that calls `experimental_subAgent()` | Files after upgrade | | --- | --- | --- | --- | --- | --- | --- | | 0.4.2 | `composio upgrade 0.4.6-beta.475` | exit 0, checksum verified | `0.4.6-beta.475` | `1`, exit 0 | try/catch script: removal message caught, exit 0. Uncaught call: same message, exit 1 | 10 legacy paths are 0 bytes, `release-tag.txt` = beta tag | | 0.3.3 | `composio upgrade 0.4.6-beta.475` | exit 0, checksum verified | `0.4.6-beta.475` | `1`, exit 0 | same | same; `generation-runtime.mjs` restored on first `run` | | 0.2.14 | `COMPOSIO_GITHUB_TAG='@composio/cli@0.4.6-beta.475' composio upgrade` | exit 0, checksum verified | `0.4.6-beta.475` | `1`, exit 0 | same | 4 `run-subagent-*.mjs` are 0 bytes; runtime modules restored on first `run` | The removal message, as printed: `experimental_subAgent() was removed from composio run because its agent transport automatically approved permission requests. Print the tool results and let the calling agent summarize them instead.` Notes: - #4732 is already in stable releases since 0.4.3. This check confirms that its placeholder files still let 0.2.14 through 0.4.2 upgrade to the current beta. - Old upgraders never delete files. After upgrading from 0.4.2 or 0.3.3, the old `services/run-subagent-*.mjs` bundles (2.4–6.3 MB) stay on disk. They are unused. - Old binaries read their GitHub settings with a `COMPOSIO_` prefix (`COMPOSIO_GITHUB_TAG`, `COMPOSIO_GITHUB_API_BASE_URL`). With a bare `GITHUB_TAG=<tag>`, 0.2.14 ignores the pin and installs the latest stable, 0.4.5. To pin a release on an old binary, set `COMPOSIO_GITHUB_TAG`, not `GITHUB_TAG`. - This machine's IP had used up GitHub's unauthenticated API quota. The old upgraders can't send a token, so their release lookups (`COMPOSIO_GITHUB_API_BASE_URL`) went through a local GET-only proxy that added a token. The asset downloads, checksum checks and file replacement ran as they do for users. ### Checks run - `bun run lint:links` (docs): 0 errors. - `bun test tests/static/` (docs): 727 pass, 5 fail. All 5 are in `content-freshness.test.ts` and fail the same way on `next`. - `prettier --check` on both changed files: clean. - `pnpm validate:changesets`: passed.