RelayStack changelog

Platform updates, SDK releases, and CLI changes for RelayStack, newest first.

Every entry notes whether it affects the API, the SDKs, the CLI, or the dashboard.

The CLI added a replay command that runs a stored production event against a local version of a workflow. Developers can compare the new trace with the original and confirm a fix before deploying, without sending anything to downstream systems.

Webhook endpoints now support signature verification with rotating secrets. You can add a new secret, accept both for a transition window, and retire the old one without dropping events or asking the sender to coordinate a cutover.

API Orchestration added per-destination rate limits. A workflow can declare a requests-per-second ceiling for each partner API, and RelayStack queues excess calls instead of failing them, which keeps bursts from triggering the partner's own limits.

The SDKs now generate typed clients from a workflow's input schema. A service that starts a run gets compile-time checks on the payload, and a renamed field shows up as a build error instead of a failed run in production.

Usage alerts can now be delivered to a webhook as well as email. Teams can post a message to a channel or open an incident when executions pass a set percentage of the plan allowance, with the current total in the payload.