<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Maintenance on preconfiguration.com</title>
    <link>https://preconfiguration.com/tags/maintenance/</link>
    <description>Recent content in Maintenance on preconfiguration.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://preconfiguration.com/tags/maintenance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Upgrade Case Study: PostgreSQL 16 to 17 in One Line, With Every Platform&#39;s Files Following</title>
      <link>https://preconfiguration.com/upgrade-case-study-postgresql-16-to-17-in-one-line-with-every-platforms-files-following/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://preconfiguration.com/upgrade-case-study-postgresql-16-to-17-in-one-line-with-every-platforms-files-following/</guid>
      <description>&lt;p&gt;Setup files are written once and changed many times. Every upgrade of a runtime or a database has to reach every file that installs it: the dev container, the Copilot workflow, the Cursor environment, the server script. Miss one, and one agent works on a different version from everyone else, which shows up later as a bug nobody else can reproduce.&lt;/p&gt;&#xA;&lt;p&gt;In the Alpha demo, the orders-api team moves from PostgreSQL 16 to 17. One line changes in &lt;code&gt;preconfig.yaml&lt;/code&gt;. &lt;code&gt;preconfig check&lt;/code&gt; lists every file that is now out of date, &lt;code&gt;preconfig build&lt;/code&gt; rewrites them, and check is clean again.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
