Recorded on November 4, 2026
Ship a release
Coroid Expo had last been deployed by hand, and Coroid had no record of what ran in production. Coroid shipped the merged work as one release: checks, a person's approval, a deploy through Expo's own workflow, the run verified on GitHub, and health judged after it.
- To the pull request
- 39 min
- Model spend
- $0.28
What was asked
Connect Expo's deploy workflow, set the release rules, release everything merged since the last deploy with its notes, have a person approve it, and let Coroid start the deploy and confirm the outcome itself.
What happened on the way
Coroid would not call the release shipped on the workflow's word alone. A mistyped deployment job name in the pipeline settings held the success back until a person corrected it and Coroid verified the run's job on GitHub.
The outcome
Shipped. Production runs the released commit, the workflow reported the new version, and the health checks passed. The deployment record lists what shipped and flags the restricted paths it touched.
The record
- Pull request #208Made by CoroidMerged as 6f66d4cd5
- 1 task recorded in Coroid
- Released as version 0.1.1
The repository is private, so this record names its pull requests and does not link them.