<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>release on Aftermarket.dev</title>
    <link>https://aftermarket.dev/tags/release/</link>
    <description>Recent content in release on Aftermarket.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aftermarket.dev/tags/release/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AfterDiff Gets a Live Shadow Mode to Test New Versions on Real Traffic</title>
      <link>https://aftermarket.dev/afterdiff-gets-a-live-shadow-mode-to-test-new-versions-on-real-traffic/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterdiff-gets-a-live-shadow-mode-to-test-new-versions-on-real-traffic/</guid>
      <description>Aftermarket 0.10.0 adds aftermarket shadow. It&amp;rsquo;s AfterDiff, but on live traffic instead of a recording.
Replay is good at one thing. You record what a client sends, play it to the old and the new version, and read the differences. But a recording only holds what happened while it ran. The odd request that comes once a week isn&amp;rsquo;t in the file, and neither is the client nobody remembered.
Shadow puts the new version next to the old one while real users keep going.</description>
    </item>
    
    <item>
      <title>Aftermarket Fixes Five Shadow Mode Bugs Found in Review</title>
      <link>https://aftermarket.dev/aftermarket-fixes-five-shadow-mode-bugs-found-in-review/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/aftermarket-fixes-five-shadow-mode-bugs-found-in-review/</guid>
      <description>Aftermarket 0.10.1 is a fix release for aftermarket shadow, the live mode of AfterDiff that came out earlier today. A second reviewer went through it looking for ways to break its promises, and found five real bugs. None of them touched what clients get back from the primary. They were about what the candidate got and what the report said.
Here&amp;rsquo;s the list.
Stopping made the candidate look broken. On Ctrl-C, shadow waits a while for queued copies and then stops.</description>
    </item>
    
    <item>
      <title>AfterBridge Released to Serve Old CSV Exports and SQLite Files as a JSON API</title>
      <link>https://aftermarket.dev/afterbridge-released-to-serve-old-csv-exports-and-sqlite-files-as-a-json-api/</link>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterbridge-released-to-serve-old-csv-exports-and-sqlite-files-as-a-json-api/</guid>
      <description>Aftermarket 0.9.0 adds AfterBridge, run as aftermarket bridge. It&amp;rsquo;s for the app that never got an API. It drops a CSV export into a folder every night, or keeps everything in a SQLite file, and anything else that wants the data has to go and parse the files.
So everyone writes their own little parser. One forgets the quoted commas, one reads the file while the app is still writing it, one treats the empty cell as zero.</description>
    </item>
    
    <item>
      <title>AfterConfig Adds TOML Overlays That Keep Every Comment</title>
      <link>https://aftermarket.dev/afterconfig-adds-toml-overlays-that-keep-every-comment/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterconfig-adds-toml-overlays-that-keep-every-comment/</guid>
      <description>Aftermarket 0.7.0 teaches AfterConfig to read and write TOML. That&amp;rsquo;s the config format of a lot of newer software: Rust and Python tools, Go services, Hugo, plenty of daemons. Their vendors replace config.toml on every upgrade, same as everyone else.
An overlay works the same way it does for JSON, YAML and .env. You list your changes by dot path, each one guarded by the value it expects, and config apply writes the result to a separate file.</description>
    </item>
    
    <item>
      <title>AfterConfig Released to Change Vendor Config Files Without Editing Them</title>
      <link>https://aftermarket.dev/afterconfig-released-to-change-vendor-config-files-without-editing-them/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterconfig-released-to-change-vendor-config-files-without-editing-them/</guid>
      <description>Aftermarket 0.4.0 adds AfterConfig, run as aftermarket config. It&amp;rsquo;s for the config file a vendor ships with its app, the one you have to change and every upgrade overwrites.
The usual fix is to edit the file and keep a note somewhere. Then the upgrade lands, the note gets forgotten, and the app runs on vendor defaults again. Or worse, someone copies the old file back over the new one and wipes out a setting the vendor added on purpose.</description>
    </item>
    
    <item>
      <title>AfterGuard Released to Put a Lock on Old Apps That Have None</title>
      <link>https://aftermarket.dev/afterguard-released-to-put-a-lock-on-old-apps-that-have-none/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterguard-released-to-put-a-lock-on-old-apps-that-have-none/</guid>
      <description>Aftermarket 0.6.0 adds AfterGuard, run as aftermarket guard. It&amp;rsquo;s for the app that was never meant to face anyone: an admin panel from 2014 with no login, an internal API with no rate limit, a debug page someone forgot to switch off.
Rewriting those apps rarely happens. The usual fix is a few lines of nginx config that nobody tests, or an IP allow list that stops working the day someone moves offices.</description>
    </item>
    
    <item>
      <title>AfterHook Released to Send Webhooks From Software That Never Had Any</title>
      <link>https://aftermarket.dev/afterhook-released-to-send-webhooks-from-software-that-never-had-any/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterhook-released-to-send-webhooks-from-software-that-never-had-any/</guid>
      <description>Aftermarket 0.5.0 adds AfterHook, run as aftermarket hook. It&amp;rsquo;s for the app that changes data and never tells anyone.
You know the kind. An order system writes its status to a file. A vendor tool drops CSV exports into a folder at odd hours. A small internal app keeps everything in SQLite and has no API at all. Something else needs to know when those things change, and the usual answer is a cron job someone wrote years ago that diffs a file and sends an email.</description>
    </item>
    
    <item>
      <title>Aftermarket Fixes Proxy Answers Cut Off Under Load</title>
      <link>https://aftermarket.dev/aftermarket-fixes-proxy-answers-cut-off-under-load/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/aftermarket-fixes-proxy-answers-cut-off-under-load/</guid>
      <description>Aftermarket 0.7.1 is a fix release, and the bug it fixes was hiding in plain sight. For a couple of days CI failed now and then in the random pass-through tests, with an &amp;ldquo;unexpected EOF&amp;rdquo; while reading an answer. The same tests passed every time on the build machine. It got written off as a flaky test.
It wasn&amp;rsquo;t. Every failure was on the call through the proxy, never on the direct one.</description>
    </item>
    
    <item>
      <title>Aftermarket Hardens Patch, Adapt and Record Against Stalled and Cut Off Uploads</title>
      <link>https://aftermarket.dev/aftermarket-hardens-patch-adapt-and-record-against-stalled-and-cut-off-uploads/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/aftermarket-hardens-patch-adapt-and-record-against-stalled-and-cut-off-uploads/</guid>
      <description>Aftermarket 0.7.2 is about one unglamorous thing: what a proxy does with a request body that doesn&amp;rsquo;t arrive the normal way. It might come slowly, stop halfway, get cut off, or still be on its way when the upstream has already answered.
That sounds like an edge case. It isn&amp;rsquo;t, once a proxy sits in front of real clients. Phones lose signal mid-upload. Scripts get killed. Some servers answer 401 before reading a byte of the body.</description>
    </item>
    
    <item>
      <title>AfterSchema Released to Keep Old SQL Working After a Schema Change</title>
      <link>https://aftermarket.dev/afterschema-released-to-keep-old-sql-working-after-a-schema-change/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterschema-released-to-keep-old-sql-working-after-a-schema-change/</guid>
      <description>Aftermarket 0.8.0 adds AfterSchema, run as aftermarket schema. It&amp;rsquo;s for the day an app&amp;rsquo;s database moves to a new shape and everything else that reads it breaks: the monthly report, the export script, the BI dashboard someone set up three years ago and nobody owns.
The app&amp;rsquo;s own code got updated with the migration. Those other readers didn&amp;rsquo;t, and usually nobody has a list of them. The fix people reach for is a few hand-written views, applied once and never tested.</description>
    </item>
    
    <item>
      <title>AfterAPI Released to Keep Old API Clients Working</title>
      <link>https://aftermarket.dev/afterapi-released-to-keep-old-api-clients-working/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterapi-released-to-keep-old-api-clients-working/</guid>
      <description>Aftermarket 0.2.0 adds a second tool. AfterAPI, run as aftermarket adapt, keeps an old client working after the API it was written for has been replaced.
AfterPatch fixes one thing at a time: a renamed field, a missing header, a moved path. That works until the whole API changes shape. Then you&amp;rsquo;d need a dozen small rules, and nobody could read them as a whole. AfterAPI takes the other approach. You write down what each old endpoint looked like, in terms of the new one, and adapt does the translating both ways.</description>
    </item>
    
    <item>
      <title>AfterTest and AfterDiff Released to Record Traffic and Compare Versions</title>
      <link>https://aftermarket.dev/aftertest-and-afterdiff-released-to-record-traffic-and-compare-versions/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/aftertest-and-afterdiff-released-to-record-traffic-and-compare-versions/</guid>
      <description>Aftermarket 0.3.0 adds two tools that work as a pair. AfterTest, run as aftermarket record, saves real traffic as test fixtures. AfterDiff, run as aftermarket replay, sends those fixtures to two versions of a service and tells you where the answers differ.
The first two tools fix things. These two answer the question that comes before any fix: what actually changed? A new release, a migrated service or a rewritten endpoint can look the same in the docs and still answer differently.</description>
    </item>
    
    <item>
      <title>AfterPatch Released as the First Aftermarket Tool</title>
      <link>https://aftermarket.dev/afterpatch-released-as-the-first-aftermarket-tool/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterpatch-released-as-the-first-aftermarket-tool/</guid>
      <description>AfterPatch 0.1.0 is out. It&amp;rsquo;s the first working tool in the Aftermarket family: a small reverse proxy that repairs HTTP traffic between a client and a service, with rules you can read, and without changing either side.
You put it in front of a service, point the client at it, and give it a YAML file of rules. A rule says which traffic it applies to (method, path, query, headers, status, content type) and what to change: set or remove headers, rewrite the path, or rename, copy, set and delete JSON fields in the request or the response.</description>
    </item>
    
  </channel>
</rss>
