Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs(cli): restore 0.3.0 and 0.3.1 changelog entries (#4048)
This PR: - restores missing `0.3.0` and `0.3.1` sections in `ts/packages/cli/CHANGELOG.md` - moves the plugin hint and telemetry changes out of `0.2.33` - records post-`0.3.1` connected-account and login fixes under `Unreleased` - rewrites the restored notes as concise, user-facing bullets - validates the ignored-package boundary with `pnpm validate:changesets`
Alberto Schiabel committed
Aug 4, 2026 at 17:10 UTC
15c07ec6c7b1b9368e668aae8e004914b9e6b082
1 file changed
+31
-7
ts/packages/cli/CHANGELOG.md
+31
-7
@@ -4,10 +4,37 @@
4
5
### Patch Changes
6
7
-- Make GitHub release metadata the sole version authority for standalone CLI
8
- binaries. Release builds now embed their exact tag version, manual skill
9
- installation follows the packaged release tag, and stable releases can only
10
- promote a tested beta.
7
+- Connected-account statuses added by the server no longer break
8
+ `connected-accounts`, `link`, or `listen`. Piped output still strips
9
+ credential fields, and schema warnings no longer print raw response values.
10
+- `composio login --poll` now reports unreadable cache files as I/O errors
11
+ instead of treating them as invalid session data.
12
+
13
+## 0.3.1
14
+
15
+### Minor Changes
16
+
17
+- The CLI now points Claude Code and Codex users to `composio setup` when the
18
+ Composio agent plugin is missing. The hint goes to stderr, appears at most
19
+ once every 24 hours, remains visible in non-TTY agent sessions, and stays
20
+ suppressed inside `composio run` children.
21
+- Telemetry now goes directly to PostHog. This captures `install` and `setup`
22
+ events before login without changing existing opt-outs.
23
+- Telemetry events now include `journey_stage` (`install`, `setup`, `login`,
24
+ `connect`, `execute`, or `other`) and `cli_channel` (`stable` or `beta`).
25
+ `install.sh` also labels `composio install` with
26
+ `invocation_origin: installer`, so script installs can be separated from
27
+ manual runs. npm and Homebrew installs do not pass through `install.sh` and
28
+ therefore have no installer origin.
29
+
30
+## 0.3.0
31
+
32
+### Patch Changes
33
+
34
+- The GitHub release tag is now the only version source for standalone CLI
35
+ binaries. Release builds embed the exact tag version, manual skill
36
+ installation uses that tag, and stable releases can only promote a tested
37
+ beta.
38
39
## 0.2.33
40
@@ -19,9 +46,6 @@
46
47
### Minor Changes
48
22
-- Cross-promote the Composio agent plugin (PRDE-1153): when the bare CLI runs inside Claude Code or Codex and the Composio plugin is not installed in that host, the CLI prints one stderr tip per 24 hours pointing at `composio setup`. The tip is deliberately visible to non-TTY (agent-driven) shells, never touches stdout, and is suppressed inside `composio run` children.
23
-- Telemetry now delivers directly to PostHog, so pre-login `install`/`setup` events are captured. Opt-outs are unchanged.
24
-- Telemetry events now carry `journey_stage` (install/setup/login/connect/execute/other) and `cli_channel` (stable/beta) properties, and `install.sh` marks its `composio install` run with `invocation_origin: installer` so script installs are distinguishable from manual ones. npm and Homebrew installs do not run `install.sh`, so their installs carry no installer origin.
49
- Make headless `composio login` agent-friendly (PRDE-1138): the non-interactive instructions now offer the unattended `composio login --agent` path, and a machine with a stored READY agent identity (`~/.composio/agent.json`) completes plain headless `composio login` unattended by reusing it. Reuse only — a human piping `composio login` still gets the URL + poll instructions and never has an account auto-created.
50
- a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`.
51
- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.