Repository navigation
Core 0.33.2 stops storing NULL when a typed value cannot be parsed. An invalid uuid, entity_link, date or timestamp value is now rejected with a 400 that names the expected format, for example invalid timestamp (expected RFC 3339 with a timezone, e.g. 2026-01-31T09:30:00Z): "2026-10-05T13:38:54".
Previously such values were bound as NULL. On a required field this surfaced as an unrelated NOT NULL violation behind a generic 500; on a nullable field the value was silently lost. Timestamps without a timezone are refused rather than assumed UTC, since only the caller knows the source's zone.
0.33.0 and 0.33.1 were withdrawn. This release builds on 0.32.1 and does not contain their changes; the version continues past them so published tags keep increasing.
Behavior change: apps that sent malformed values to nullable typed fields now receive a 400 instead of a silent NULL. Send RFC 3339 timestamps with an offset (Z or +02:00), YYYY-MM-DD dates and canonical UUID strings.
Migration: none. Image-only rollback to 0.32.1 is supported.
Validation: 513 library tests passed; 282 of 283 integration tests passed, the remaining lifecycle-lock timing test passed on three isolated reruns. The published image booted cleanly against a fresh RootCX PostgreSQL. No CLI, Studio, SDK or crates.io release accompanies this Core-only release.