<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Release-Engineering on Mornati Blog</title><link>https://blog.mornati.net/tags/release-engineering/</link><description>Recent content in Release-Engineering on Mornati Blog</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>© 2026 Marco Mornati</copyright><lastBuildDate>Tue, 20 Oct 2026 16:00:00 +0000</lastBuildDate><atom:link href="https://blog.mornati.net/tags/release-engineering/rss.xml" rel="self" type="application/rss+xml"/><item><title>Your Agents Ship Fast. Make Them Pass a Release Gate First</title><link>https://blog.mornati.net/your-agents-ship-fast-make-them-pass-a-release-gate/</link><pubDate>Tue, 20 Oct 2026 16:00:00 +0000</pubDate><guid>https://blog.mornati.net/your-agents-ship-fast-make-them-pass-a-release-gate/</guid><description>Before tagging ai-finance-coach 1.0.0, one command found my first name in a test, an employer in a test id and one of my own figures in the demo data, all in a repository with green CI. What leaks when agents work with real data, why CI and secret scanners can&amp;rsquo;t see it, and the generic recipe I use now - one scripted release gate, a local term file that never enters the repository, and four places that force everyone, agents included, to run it.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://blog.mornati.net/your-agents-ship-fast-make-them-pass-a-release-gate/cover.jpg"/></item></channel></rss>