Deployments
Prepare a release, run your existing deployment process in a session, and check the result.
Use Alan sessions to prepare releases, run your repository's deployment commands, and check the result. Deployment still uses your existing scripts or pipeline; Alan does not provide a separate release dashboard.
Before the release
- Merge-ready pull requests. Check review state, Required checks, and conflicts on the pull request page, then merge from Merge. See Pull requests.
- Evidence. Each linked task should have a test report that matches what the pull request claims. See Testing evidence.
- A release summary. Ask an agent to list what's going out. For example: "List the pull requests merged into main since the last release tag, with linked tasks and any known risks."
Running your own deploy steps
If your repository has its own deploy scripts or a repository skill such as /deploy, an agent can run them in a session like any other command, with the access that session's computer or cloud environment has. Alan doesn't add approvals, environments, or rollback on top. Keep production credentials and approvals in your deploy pipeline.
After the release
Ask an agent to run the narrowest check that proves the change is live, for example loading the changed route or calling a health endpoint, and to file a test report with what passed, what was skipped, and what still needs watching.
To run the same post-release check every time, create an automation, for example one triggered by Pull Request Merged.