You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changed
Cratis.Chronicle/Cratis.Chronicle.AspNetCore/Cratis.Chronicle.Testing bumped from 18.2.0 to 19.4.2 to pick up [Encrypted] and the read-model release fix it depends on; Cratis.Fundamentals/Cratis.Metrics.Roslyn bumped from 7.19.2 to 7.19.3 alongside it
Fixed
A read model injected into a command's Handle(), Provide(), or a CommandValidator<T> is now released (its [PII]/[Encrypted] properties decrypted) regardless of whether the command declares a Subject/[Subject]/ICanProvideSubject — most commands rely on Chronicle's implicit event-source-id subject fallback instead, which was never checked, so release was silently skipped for the common case independent of what the injected read model actually carried
A namespace- or global-scoped [Encrypted] value (Cratis/Chronicle#4095) now reaches release correctly even on a read model that has no Id/[Subject] at all — the ordinary shape for that kind of value, since its key does not depend on a subject