DataHub 1.4.3

DataHub 1.4.3

Fixes parent-object merge rules not applying to descendant properties in tracked
updates, untracked updates, and first-time merges into existing entities.

Property rules now resolve in this order: exact property, nearest configured
ancestor, then *. Explicit child rules can override parent rules in either
direction. Matching remains case-insensitive and respects dot-delimited path
boundaries.

Behavioral compatibility

Existing parent rules now govern descendants that previously fell through to the
wildcard or the handler's no-match behavior. For example, Venue: AlwaysOverwrite
with *: NeverOverwrite now permits changes to Venue.EntityId; conversely,
Venue: NeverOverwrite protects its descendants even with a permissive wildcard.
Review existing parent/child rule combinations before upgrading if you relied on
the previous behavior. Explicit descendant rules remain supported.

Public APIs, configuration schemas, and notification payloads are unchanged.
Existing action execution, null handling, and array semantics are preserved.
The untracked update handler's existing conditional-action limitations remain.

Validation

• 813 unit tests passed, including 310 new merge-rule regression cases.
• All seven Cosmos merge-rule integration scenarios passed, including a persisted
  season-to-venue update that preserves identity, managed fields, and alternate keys.

All 11 public DataHub packages share version 1.4.3. Publishing this release does not
automatically upgrade consuming applications or deploy them.