Composio HQ CLI Release
Use this skill for the GitHub Release that powers the standalone composio binary and installer.
Read references/release-workflow.md before selecting a candidate or dispatching a workflow.
Release Contract
- Never add a Changeset for
@composio/clior@composio/cli-local-tools; both packages are ignored by Changesets and such files wedgets.release.yml. - Treat a merge to
nextthat touches CLI paths as a beta build. Promote a tested beta with thepromote-stableworkflow action for the normal stable-release path. - Never bump the private CLI
package.jsonto select a binary version. For an intentional minor or major, build an explicitly versioned beta and promote that tested beta through the same stable path. - Resolve beta tags and workflow state from GitHub immediately before acting. Never invent or reuse a stale candidate from memory.
- 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.
- Follow the release through asset verification and installation tests. Do not stop after the dispatch succeeds.
Execution
- Classify the request as automatic beta, manual beta, stable promotion, or recovery.
- Run the playbook's read-only preflight and identify the exact source commit and release tag.
- Dispatch only the requested workflow action and watch the resulting run to completion.
- Verify the published release and downstream checks named in the playbook.
- Report the released tag, source beta or commit, workflow URL, asset state, install-test result, and any remaining follow-up.