<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Upgrades on CodeInstances.com</title>
    <link>https://codeinstances.com/tags/upgrades/</link>
    <description>Recent content in Upgrades on CodeInstances.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://codeinstances.com/tags/upgrades/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Upgrade a Dependency With CodeInstances Replaying Real Runs</title>
      <link>https://codeinstances.com/how-to-upgrade-a-dependency-with-codeinstances-replaying-real-runs/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://codeinstances.com/how-to-upgrade-a-dependency-with-codeinstances-replaying-real-runs/</guid>
      <description>&lt;p&gt;You need to bump something underneath your program. A new major version of the HTTP client library, a vendor&amp;rsquo;s SDK, or the Go toolchain itself. The changelog is long. Your unit tests pass, but they use mocks written two years ago against the old behaviour, so passing doesn&amp;rsquo;t tell you much. What you&amp;rsquo;d like to know is simple: does the program still do the same thing on real work?&lt;/p&gt;&#xA;&lt;p&gt;Real runs answer that. Before the upgrade, record a handful of runs of the current build doing real work, against the real services:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
