Release v19.106.0

Summary

Webhooks registered before target validation existed are now checked against the current policy too. Adding an event-type generation backfills revised events from their latest revision. Test event stores generate each event schema once per process.

Added

• Test event stores (EventStoreForTesting, and through it ReadModelScenario and the scenario defaults) share one JSON schema generator per process when they use the default service provider, so suites that create many stores generate each event schema once. Each store still gets its own copy of every schema. Set EventStoreForTesting.ShareSchemaGenerator = false to opt out, for example when metadata providers keep per-store state. (#5252)

Changed

• Stored, active webhooks are checked against the current target policy before their observer subscribes, including after a restart. In Enforce, a rejected target or OAuth authority puts the observer in quarantine with the reason logged. The webhook definition and its active flag are left unchanged. In Warn, the default, the violation is logged once per activation and delivery continues. (#5107)
• Clearing a webhook observer's quarantine checks the policy again first, so the observer stays paused while its target is still not allowed. Fix the target, the allowed hosts or the validation mode, then clear the quarantine. (#5107)
• A delivery rejected by the target policy when connecting, for example because the host now resolves to a private address, pauses the webhook observer as a configuration problem instead of being retried for the 24-hour retry budget. (#5107)

Fixed

• Adding a new generation to an event type now builds the backfilled content of a revised event from its latest revision instead of the content it was first appended with, the same way on MongoDB, SQL and in-memory storage. Observers that read the backfilled generation now see the revised values. (part of #4976)