<?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 ForgeSchema.com</title>
    <link>https://forgeschema.com/tags/release/</link>
    <description>Recent content in Release on ForgeSchema.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://forgeschema.com/tags/release/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ForgeSchema Builds Indexes Online and Plans Drops and Type Changes</title>
      <link>https://forgeschema.com/forgeschema-builds-indexes-online-and-plans-drops-and-type-changes/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://forgeschema.com/forgeschema-builds-indexes-online-and-plans-drops-and-type-changes/</guid>
      <description>&lt;p&gt;ForgeSchema 0.3.0 is out. It&amp;rsquo;s the first release that isn&amp;rsquo;t labelled alpha, and the first one that went out on its own: bump the version, push, and CI builds, checks and publishes it once the tests pass on PostgreSQL 16.10 and 17.6.&lt;/p&gt;&#xA;&lt;p&gt;Three things changed. Indexes can be built without blocking writes. Check constraints are understood. And drops and type conversions are finally possible, but only when you ask for them by name.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ForgeSchema Second Alpha Handles Real PostgreSQL Schemas</title>
      <link>https://forgeschema.com/forgeschema-second-alpha-handles-real-postgresql-schemas/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://forgeschema.com/forgeschema-second-alpha-handles-real-postgresql-schemas/</guid>
      <description>&lt;p&gt;The first alpha could only read a schema if it had no defaults, no identity columns, no unique constraints and no foreign keys. That&amp;rsquo;s almost no real database. Point it at a typical app schema and it said &amp;ldquo;unsupported&amp;rdquo; and stopped.&lt;/p&gt;&#xA;&lt;p&gt;v0.2.0-alpha.1 fixes that.&lt;/p&gt;&#xA;&lt;p&gt;ForgeSchema now reads and writes varchar, char and numeric columns, defaults like &lt;code&gt;now()&lt;/code&gt;, &lt;code&gt;current_date&lt;/code&gt; and &lt;code&gt;gen_random_uuid()&lt;/code&gt;, identity columns, unique constraints, unique indexes and foreign keys with their ON DELETE and ON UPDATE actions. Inspect, plan, apply and verify all understand them. The &lt;a href=&#34;https://github.com/ForgeSchema/forgeschema/blob/main/examples/shop.yaml&#34;&gt;shop example&lt;/a&gt; uses every one: customers with an identity key and a unique email, orders that reference customers, order lines that cascade when an order goes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
