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, 06:00 UTC
fix(release): tag merged release PRs under GitHub API 2026-03-10 (#5274)
This PR: - fixes the tag gate, which recorded the first merged release PR (https://github.com/ComposioHQ/composio/pull/5261) as `Abandoned` and created no tag - API version `2026-03-10` no longer returns `merge_commit_sha` on pull responses, so the gate read every merged PR as unmerged - `mergeCommitOf()` now reads the merge commit from the PR's `merged` issue event - replaces the release-head committer check, which no real release could pass: GitHub commits and signs every API-made commit as `web-flow`, never as the App - `isReleaseAppCommit()` now requires the App to be the last actor that set the release branch to the reviewed head, from the repository activity log. A writer can make a signed `web-flow` commit naming the App as author, but can't forge that log - updates the controller fixtures to the response shapes GitHub returns today (no `merge_commit_sha`, `web-flow` committer, activity and issue-event routes) ## Context Verified against live data: the fixed gate passes #5261 (App commit, olearycrew's approval, all candidate checks green, merge commit `7beddc0`), and `candidates.ts approve` pins both the npm and PyPI candidates of that release. The tag job runs `next` as it was before the merge, so #5261 itself can't be re-gated. It has to be reverted and requested again once this lands.