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, 07:15 UTC
| 1 | --- |
| 2 | name: cli-release |
| 3 | description: Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version, choose a release candidate, monitor a CLI release, or diagnose a failed CLI release. Do not use for TypeScript SDK Changesets releases or CLI source implementation. |
| 4 | --- |
| 5 | |
| 6 | # CLI Release |
| 7 | |
| 8 | Use this skill for the GitHub Release that powers the standalone `composio` binary and installer. |
| 9 | |
| 10 | Read `references/release-workflow.md` before selecting a candidate or dispatching a workflow. |
| 11 | |
| 12 | ## Release Contract |
| 13 | |
| 14 | - Never add a Changeset for `@composio/cli`; the package is ignored by Changesets and such files wedge `ts.release.yml`. |
| 15 | - Treat a merge to `next` that touches CLI paths as a beta build. Promote a tested beta with the `promote-stable` workflow action for the normal stable-release path. |
| 16 | - Never bump the private CLI `package.json` to select a binary version. For an |
| 17 | intentional minor or major, build an explicitly versioned beta and promote |
| 18 | that tested beta through the same stable path. |
| 19 | - Resolve beta tags and workflow state from GitHub immediately before acting. Never invent or reuse a stale candidate from memory. |
| 20 | - A stable promotion is a production write. If the user did not name the exact beta tag, present the resolved candidate and obtain explicit confirmation before dispatching it. |
| 21 | - Follow the release through asset verification and installation tests. Do not stop after the dispatch succeeds. |
| 22 | |
| 23 | ## Execution |
| 24 | |
| 25 | 1. Classify the request as automatic beta, manual beta, stable promotion, or recovery. |
| 26 | 2. Run the playbook's read-only preflight and identify the exact source commit and release tag. |
| 27 | 3. Dispatch only the requested workflow action and watch the resulting run to completion. |
| 28 | 4. Verify the published release and downstream checks named in the playbook. |
| 29 | 5. Report the released tag, source beta or commit, workflow URL, asset state, install-test result, and any remaining follow-up. |