Skip to content
Aurora Catalyst

Preservation regions removed

Auto-generated from the source archive. Do not edit by hand — rerun catalyst-changelog-sync instead.

What changed

Section titled “What changed”
  • Breaking: the AURORA:FORM-FIELDS preservation region — the only one the codegen shipped — and the entire region engine are removed. Generated files no longer carry region markers.
  • File integrity is now a plain whole-file sha1, and .origin reconciliation becomes the single seam for customizing generated code.
  • Scalar-array fields carrying a relational widget now emit their options input correctly.

Why it matters

Section titled “Why it matters”

The region was meant to protect your custom form HTML across regenerations, but it also froze that block: when the template’s markup improved, the change never propagated to existing modules. That is the trade you are escaping. From now on every generated file follows one uniform rule, and you keep custom edits through catalyst origin diff / accept / reject. On the first catalyst generate after upgrading, existing forms produce an .origin to review — standard forms accept trivially, and any custom body is re-applied from the diff.

View original proposal