1.4 KiB
Narratio v2.1.1
This release fixes configuration loading for publish rules that explicitly set requiredness while relying on a derived destination.
Summary
Publish rules with a derivable source and omitted dest now load correctly
whether required is omitted, explicitly true, or explicitly false. Previously,
explicit requiredness could trigger ConfigKit's resolve.unrecorded_change
diagnostic instead of accepting valid configuration.
Compatibility
This is a backward-compatible bookkeeping correction. Publish schemas, destination derivation, requiredness defaults, and YAML syntax support are unchanged. Explicit destinations and explicit false values remain intact. No ConfigKit upgrade or publication/storage behavior change is involved.
Upgrade
No special upgrade action or configuration migration is required. Operators
need not add a derivable dest, remove explicit required values, or change
flow-style YAML to block-style YAML. See the
configuration reference.
Changes
- Recorded derived publish destinations at ConfigKit's atomic sequence boundary while retaining field-level resolution records.
- Added real load/validation and safe effective-configuration regression coverage for built-in and configured-artifact sources, explicit requiredness, and an explicit destination that must remain unchanged.