Release checks

Nothing ships unchecked

On real software teams, CI is the safety net: every change must pass the project's own checks before it reaches production. Spaceboy gives you the same discipline, fully automated. Production never ships from a direct push — every release goes through a pull request that must pass the repository's release checks (install, lint, tests) before it merges, and the production build itself is the final backstop.

How a release works

Whether you ask to go live — from the Deploy button, chat, Slack, or the CLI — or a finished task promotes its own work, Spaceboy ships it the same way:

• Opens a pull request from your environment's branch into the production line.
• The repository's own release checks run — install, lint, tests — and a red check blocks the release with the check's output as the findings.
• If a check fails, the authoring agent gets one automated pass to fix exactly what was flagged, and the checks run again.
• On green checks, the pull request merges and your production deploy starts automatically.

The checks are deterministic — the same commands an engineer would run before merging — so a finished piece of work lands on main and deploys within minutes, and a broken one is blocked with the exact failing output.

You can watch every step live on the Code Review page, in Slack, or in your terminal.

When the checks stay red

If the checks still fail after the automated fix pass, the release is rejected — nothing ships. The pull request stays open with the failing output, so you can read exactly what broke, ask your agent to address it in your workspace, and deploy to production again when it's ready.

A complete record

Every release is fully recorded: the pull request, each check run with its findings, any fix commits, the merge, and the production deploy. The Code Review page shows a live timeline for each release, and every step also lands in your organization's audit log — so you always know exactly what shipped, who asked for it, and what the checks said.