<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
  <title>PatchFlow Blog</title>
  <link>https://patchflow.run/blog</link>
  <description>Measured SDK migrations, CI trust boundaries, and dependency engineering.</description>
  <language>en-au</language>
  <item>
    <title>Our first measured migration: TypeScript 5.9 to 6.0</title>
    <link>https://patchflow.run/blog/first-measured-typescript-migration</link>
    <guid isPermaLink="true">https://patchflow.run/blog/first-measured-typescript-migration</guid>
    <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    <description>What a real private-pilot migration cost, where it failed, and why a red check was the most useful result.</description>
  </item>
  <item>
    <title>Dependency bots stop where the engineering starts</title>
    <link>https://patchflow.run/blog/dependency-bots-stop-at-the-hard-part</link>
    <guid isPermaLink="true">https://patchflow.run/blog/dependency-bots-stop-at-the-hard-part</guid>
    <pubDate>Wed, 29 Jul 2026 00:00:00 GMT</pubDate>
    <description>Version detection is useful. Breaking upgrades still leave teams with evidence gathering, call-site changes, and CI interpretation.</description>
  </item>
  <item>
    <title>A green CI badge is meaningless without a commit</title>
    <link>https://patchflow.run/blog/commit-bound-ci-verdicts</link>
    <guid isPermaLink="true">https://patchflow.run/blog/commit-bound-ci-verdicts</guid>
    <pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate>
    <description>Why migration verdicts must be bound to immutable pull-request heads—and what to do when the base branch advances.</description>
  </item>
</channel></rss>
