Skip to content

Release v16.24.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Aug 18:42
v16.24.1
c41d214
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

A [PII] value sitting alongside a geospatial value made compliance handling fail — the append was rejected and the projection partition stalled, so the read model never caught up.

Fixed

  • Applying or releasing compliance no longer fails with CompliancePropertyNotFoundInSchema when a read model or event carries a [PII] value alongside a geospatial Point, LineString or Polygon; the geospatial value is left in the clear (#3673)

Changed

  • Geospatial documentation now describes the JSON schema Chronicle emits — a leaf carrying only its format, with GeoJSON on the wire — and records that marking a geospatial value [PII] is not supported, since an erased subject cannot be materialized back into one (#3673)
Assets 2
Loading