@composio/core@0.28.0: Release: update version ( 5070)
Composio releases published @composio/core@0.28.0: Release: update version ( 5070). This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR…
Why this signal matters
Composio releases published @composio/core@0.28.0: Release: update version ( 5070). This automated release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated. Releases @composio/core@0.28.0 Minor Changes d2d4148 : Requires @composio/client 2.0.0 . POST and PATCH requests, including tool execution and trigger creation, are now sent once instead of being retried on a lost response or a retryable status, because a write can complete on the server after its response is lost. Other requests keep their retries. On the client returned by getClient() , a write retries only when that call sets maxRetries . e87ed85 : Requires @composio/client 2.0.0-rc.20 . The SDK imports the client's types from the one @composio/client/resources/ spelling rc.20 publishes and…
Actionable summary
Treat @composio/core@0.28.0: Release: update version ( 5070) as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent usefulness
- 77/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Review the official Composio releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.