What changes
Before and after
The classic way
- Releases wait for a train and a change board; the batch is large because the ceremony is expensive.
- What is in the build is whatever the build machine had; nobody can prove it.
- Rollback is a plan on paper.
The AI way
- Every build carries provenance. SLSA v1.1's build track exists so that an artifact can be verified as built as expected; at Build L1 the package has provenance showing how it was built, L2 means forging it requires an explicit attack, L3 that forging it requires exploiting a vulnerability [5].
- The change volume AI brings is the risk. DORA 2025 found AI adoption positively related to throughput but still negatively related to delivery stability, because more change without robust controls means instability [1]. Its model names the controls: strong version control with frequent commits and frequent rollback, and working in small batches [2].
- The agent drafts the release notes and the risk summary; a protected environment with a required reviewer is the only path to production, as the deploy workflow in the AI SDLC example shows [10].
Step by step
The three steps of Release
- 1
Build once, attest AI
Main is built once; the artifact is signed and its provenance recorded, so what reaches production is verifiably what was tested [5].
- 2
Canary and verify AI
The build goes to staging through short-lived cloud credentials, then to a canary slice of production, while an agent compares its signals with the baseline and drafts the release notes [10].
- 3
A person opens production Gate
The production environment requires a reviewer. The agent has prepared everything it can; the approval is a human act, logged with a name [10].
The gate
A protected production environment with a required reviewer, and rollback as a button that has been pressed before, not a document.
What the AI does here
Builds, attests, promotes to canary, watches the canary, drafts release notes and the rollback plan, and never holds the production approval.
Tools people use at this stage
- GitHub Actions and environments
- Sigstore and in-toto attestations
- Argo CD and Flux
- Jenkins
- feature flags
Named as examples, not endorsements; the center is not affiliated with any of them.
What this stage adds
The risks, and the practices that answer them
Each risk is a weakness in the Learning Center, with the incidents where it happened; each practice has its sources there.
Risks
- No human approval for consequential actionsThe release gate is automated away.
- Unpinned AI dependencies and compromised maintainer releasesAn unpinned dependency changes under the build.
- Unverified model provenanceA model artifact ships with no provenance.
Read for this stage
Sources
- [5] SLSA v1.1: security levelsread 2026-10-27
- [1] Google Cloud: Announcing the 2025 DORA State of AI-assisted Software Development reportread 2026-10-27
- [2] Google Cloud: Introducing the DORA AI Capabilities Modelread 2026-10-27
- [10] AI Test Automation: the AI SDLC on GitHub (this site)