What is changing? What is missing? Who has reviewed the next move?
Track a web application, API, and background worker as separate release records. Review the checks and dependencies before marking each version ready.
Illustrative use: prepare a monthly application release and keep the rollback question next to the release notes.
Filter by project and stage to review your own records. Owner labels help describe responsibility; they do not invite colleagues or represent an electronic approval signature.
Illustrative use: review which releases still have blockers before the next planning conversation.
Keep version context and readiness notes in a focused record. Export the information to support a conversation through the channels you already use.
Illustrative use: prepare a release summary for a client’s engineering review without claiming that Relay deploys or approves it.
Examples are illustrative. Each current account has an individual workspace. Shared team workspaces and integrations are planned.