<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Patch-Bumps on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/patch-bumps/</link><description>Recent content in Patch-Bumps on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Tue, 20 Oct 2026 08:00:00 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/patch-bumps/index.xml" rel="self" type="application/rss+xml"/><item><title>Two releases in four minutes: why release.yml fires twice</title><link>https://startaitools.com/posts/two-releases-in-four-minutes-the-asset-commit-fires-release-yml-again/</link><pubDate>Tue, 20 Oct 2026 08:00:00 -0600</pubDate><guid>https://startaitools.com/posts/two-releases-in-four-minutes-the-asset-commit-fires-release-yml-again/</guid><description>&lt;h2 id="two-releases-in-four-minutes-again"&gt;Two releases in four minutes, again&lt;/h2&gt;
&lt;p&gt;Two releases landing four minutes apart on the same host day look like a bot double-bumping a busted tag on the Releases page, until you read origin (the canonical, GitHub-hosted copy of the git remote) master and see the assets-trailing-post shape. release.yml, the GitHub Actions workflow that stamps a semver tag on every push to master, fires on every push. On this repo the post commit and the social-card assets commit are always two events.&lt;/p&gt;</description></item></channel></rss>