<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>EvalShift blog</title>
    <link>https://evalshift.dev/blog</link>
    <description>Field notes on migrating LLM models safely: golden suites, paired evaluation, regression gates in CI, and evaluator reliability.</description>
    <language>en</language>
    <atom:link href="https://evalshift.dev/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>How to test an LLM model migration before you ship it</title>
      <link>https://evalshift.dev/blog/test-llm-model-migration-before-you-ship</link>
      <guid isPermaLink="true">https://evalshift.dev/blog/test-llm-model-migration-before-you-ship</guid>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
      <description>A repeatable method for proving a model swap is safe: freeze a golden suite, run both models paired, and read the diff before your users do.</description>
    </item>
    <item>
      <title>LLM regression testing in CI: gate pull requests on eval diffs</title>
      <link>https://evalshift.dev/blog/llm-regression-testing-in-ci</link>
      <guid isPermaLink="true">https://evalshift.dev/blog/llm-regression-testing-in-ci</guid>
      <pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate>
      <description>Wire a golden suite into GitHub Actions so every pull request gets a paired eval run, a base-branch diff, and a check that fails on real regressions.</description>
    </item>
    <item>
      <title>When to trust an LLM judge</title>
      <link>https://evalshift.dev/blog/when-to-trust-an-llm-judge</link>
      <guid isPermaLink="true">https://evalshift.dev/blog/when-to-trust-an-llm-judge</guid>
      <pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate>
      <description>LLM judges are useful and easy to fool. Where pairwise judging holds up, where it breaks, and how to stop a judge from silently deciding your migration.</description>
    </item>
  </channel>
</rss>
