- Shipped
- 28 Agosti 2026, 02:16 UTC
- Author
- Kamo
- Commit
- 424e412
The column was always nullable and both server paths already handled null — CreateOrganizationPayloadParser maps an empty or unparseable value to null, and patchOrganization applies only the keys a PUT body actually mentions, so "yearEst": null is a deliberate clear while omitting the key leaves the stored value alone. None of that was written down, so the create wizard in kamo-internal had been gating on the field as if the entity required it. No behaviour change: nullable = true is the default this restates explicitly.