Release v16.12.0
Summary
Releasing PII now degrades a single unreadable property instead of failing the whole read.
Added
- Several event types declared under the same constraint name form one constraint allowing at most one event from that set per event source, making mutually exclusive outcomes enforceable at append time.
CHR0039warns when aTask-returning testing assertion is discarded rather than awaited, where it can never fail andCS4014does not fire.
Changed
- A
[PII]value that Chronicle never encrypted is passed through untouched when releasing, instead of being blanked.
Fixed
- Releasing a
[PII]value encrypted under a different subject no longer fails the whole read model and the query returning it. That property is surfaced as empty and the diagnostic goes to the Kernel log. - Releasing a
[PII]value for a subject that never had an encryption key no longer returns an empty value indistinguishable from crypto-shredded erasure.