<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Releases on Preconfiguration.com</title>
    <link>https://preconfiguration.com/tags/releases/</link>
    <description>Recent content in Releases on Preconfiguration.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://preconfiguration.com/tags/releases/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Preconfig 0.2 Sets Up Machines for Claude Code, Codex, Ona and Devin From the Same Spec</title>
      <link>https://preconfiguration.com/preconfig-0.2-sets-up-machines-for-claude-code-codex-ona-and-devin-from-the-same-spec/</link>
      <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://preconfiguration.com/preconfig-0.2-sets-up-machines-for-claude-code-codex-ona-and-devin-from-the-same-spec/</guid>
      <description>&lt;p&gt;Five targets covered the platforms that were reading setup files when preconfig started: dev containers, GitHub Copilot, Cursor, cloud-init and a plain script. Since then the agent platforms people actually use have moved on. Version 0.2 adds four more, written from each platform&amp;rsquo;s own documentation as it stood on November 4, 2026.&lt;/p&gt;&#xA;&lt;p&gt;The first thing the documentation showed is that the four don&amp;rsquo;t work alike. Ona and Devin read a file from the repository. Claude Code and Codex keep a machine&amp;rsquo;s setup in their own settings, so a spec can&amp;rsquo;t simply be compiled into a file they pick up. Each target does what its platform allows.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Preconfig Now Checks Agent Setup Files on Every Pull Request</title>
      <link>https://preconfiguration.com/preconfig-now-checks-agent-setup-files-on-every-pull-request/</link>
      <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://preconfiguration.com/preconfig-now-checks-agent-setup-files-on-every-pull-request/</guid>
      <description>&lt;p&gt;A setup file for a coding agent breaks quietly. Someone bumps Python in the dev container and forgets the Copilot workflow, or edits the generated setup script by hand, and nobody finds out until an agent spends its first ten minutes failing to install a package. Preconfig 0.3 moves that discovery to the pull request.&lt;/p&gt;&#xA;&lt;p&gt;It ships as a GitHub Action, added to a workflow like this:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;on&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;pull_request&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;jobs&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;preconfig&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;runs-on&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;ubuntu-latest&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;steps&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;      - &lt;span style=&#34;color:#f92672&#34;&gt;uses&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;actions/checkout@v7&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;      - &lt;span style=&#34;color:#f92672&#34;&gt;uses&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;Preconfiguration/preconfig@v0.3.1&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id=&#34;what-it-does-on-a-pull-request&#34;&gt;What It Does on a Pull Request&lt;/h2&gt;&#xA;&lt;p&gt;The action downloads the release for the runner and checks it against the release&amp;rsquo;s checksums before running anything. Then it runs &lt;code&gt;preconfig check&lt;/code&gt;. Each problem shows up as a mark on the line it&amp;rsquo;s about, in the pull request&amp;rsquo;s file view, and a table of all of them goes into the job summary. A Cursor environment file with a key Cursor doesn&amp;rsquo;t read, a setup script that no longer matches &lt;code&gt;preconfig.yaml&lt;/code&gt;, an Ona task with no command: each one lands where the reviewer is already looking.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
