v5.12.0

⚠️ Breaking Changes

• Node default values are now strictly validated at application startup. If a node defines a field (e.g., ImageField) with a default value that does not match the field type (e.g., default=None), the application will error on startup. Fix by either updating the type annotation to include None (e.g., ImageField | None) if the field is optional, or by removing the invalid default or providing a valid default value that satisfies the field constraints (e.g., for an integer field with gt=10, the default must be > 10).