<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>The Releo blog</title>
  <link>https://tryreleo.com/blog</link>
  <description>Engineering notes on shipping API changes safely.</description>
  <language>en</language>
  <atom:link href="https://tryreleo.com/rss.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>Inside a behavioral diff: what to compare and what to ignore when replaying API traffic</title>
    <link>https://tryreleo.com/blog/api-traffic-replay-behavioral-diff</link>
    <guid>https://tryreleo.com/blog/api-traffic-replay-behavioral-diff</guid>
    <pubDate>Wed, 21 Oct 2026 09:00:00 GMT</pubDate>
    <category>Engineering</category>
    <description>A behavioral diff is only useful if it ignores noise and catches real changes. How to normalize IDs, timestamps, ordering, headers, latency and secrets.</description>
  </item>
  <item>
    <title>Deterministic verification vs LLM-as-judge for code changes</title>
    <link>https://tryreleo.com/blog/deterministic-verification-vs-llm-as-judge</link>
    <guid>https://tryreleo.com/blog/deterministic-verification-vs-llm-as-judge</guid>
    <pubDate>Wed, 07 Oct 2026 09:00:00 GMT</pubDate>
    <category>Engineering</category>
    <description>A model grading its own patch is not evidence. Why code changes need deterministic, reproducible verification, and where LLMs still earn their place.</description>
  </item>
  <item>
    <title>How API providers can cut their customers' migration time</title>
    <link>https://tryreleo.com/blog/reduce-api-migration-time-for-customers</link>
    <guid>https://tryreleo.com/blog/reduce-api-migration-time-for-customers</guid>
    <pubDate>Wed, 16 Sep 2026 09:00:00 GMT</pubDate>
    <category>Guides</category>
    <description>Every breaking change costs your customers engineering time. Machine-readable changelogs, OpenAPI diffs, codemods and automated PRs shrink that cost.</description>
  </item>
  <item>
    <title>Why AI agents make API changes more dangerous</title>
    <link>https://tryreleo.com/blog/ai-agents-api-changes-schema-drift</link>
    <guid>https://tryreleo.com/blog/ai-agents-api-changes-schema-drift</guid>
    <pubDate>Wed, 02 Sep 2026 09:00:00 GMT</pubDate>
    <category>AI</category>
    <description>AI agents call tools backed by real APIs. When those APIs drift, agents fail quietly or act confidently wrong. Here is how to version, check and replay.</description>
  </item>
  <item>
    <title>How to ship a breaking API change without burning your consumers</title>
    <link>https://tryreleo.com/blog/how-to-ship-a-breaking-api-change-checklist</link>
    <guid>https://tryreleo.com/blog/how-to-ship-a-breaking-api-change-checklist</guid>
    <pubDate>Wed, 19 Aug 2026 09:00:00 GMT</pubDate>
    <category>Guides</category>
    <description>A provider checklist for breaking API changes: announcing, Deprecation and Sunset headers, precise changelogs, migration tooling, dual running and removal.</description>
  </item>
  <item>
    <title>Your tests passed. Your migration still broke production.</title>
    <link>https://tryreleo.com/blog/api-migration-tests-passed-production-broke</link>
    <guid>https://tryreleo.com/blog/api-migration-tests-passed-production-broke</guid>
    <pubDate>Wed, 05 Aug 2026 09:00:00 GMT</pubDate>
    <category>Engineering</category>
    <description>Mocks encode the old API, so migration tests pass while production breaks. A worked billing example shows behavioral vs contract breaks and how to catch both.</description>
  </item>
  <item>
    <title>The hidden cost of an API breaking change, for the people who consume it</title>
    <link>https://tryreleo.com/blog/hidden-cost-of-api-breaking-changes</link>
    <guid>https://tryreleo.com/blog/hidden-cost-of-api-breaking-changes</guid>
    <pubDate>Wed, 22 Jul 2026 09:00:00 GMT</pubDate>
    <category>Engineering</category>
    <description>An API breaking change looks like a one-line fix. For consumers the hours go to discovery, finding call sites, patching, verifying, rollout and incidents.</description>
  </item>
  <item>
    <title>Why API change verification needs to be its own category</title>
    <link>https://tryreleo.com/blog/why-api-change-verification-needs-to-exist</link>
    <guid>https://tryreleo.com/blog/why-api-change-verification-needs-to-exist</guid>
    <pubDate>Wed, 08 Jul 2026 09:00:00 GMT</pubDate>
    <category>Company</category>
    <description>Detecting API breaking changes is largely solved and patches are getting easier to write. Proving a migration did not change behavior is the missing step.</description>
  </item>
</channel>
</rss>
