Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 18:30 UTC
fix(release): drop stale changeset for ignored `@composio/cli` (#3861)
This PR: - unblocks #3820 — the `0.14.0` release train (including `@composio/experimental@0.2.0` with the `./eve` export) is versioned on `next` but was never published to npm - deletes `.changeset/cli-file-upload-denylist.md`: it targets `@composio/cli`, which is in the changesets `ignore` list (since #3676), so `changeset version` never consumes it - the leftover changeset makes `changesets/action` pick version-PR mode over publish mode on every push to `next`, then fail with `No commits between next and changeset-release/next` because the versioning no-ops — see the [failed run](https://github.com/ComposioHQ/composio/actions/runs/29449907252/job/87469539026); the publish step never executes - ports the security note from the deleted changeset into the `0.3.0` section of `ts/packages/cli/CHANGELOG.md` — the fix commit (fc17c37bf, #3763) is part of the `0.3.0` tree, and `@composio/cli@0.3.0` has no tag/release yet ## Context Once this merges, the next `TS SDK Release` run on `next` will find no pending changesets, take the publish path (`pnpm changeset:release`), and push the pending versions to npm. Follow-up worth considering (not in this PR): a CI check that rejects changesets referencing packages in the `ignore` list, since any such changeset permanently wedges the release train.