A changelog link is not enough when rollout scope changes

A documentation note about comparing changelog entries by release date, version, plan, region, and rollout status.

For product features, one changelog entry may introduce a beta and another may expand it to paid plans or all regions. Linking both is not enough unless the note says how they relate. I want the source trail to say whether the later entry replaces, narrows, or extends the earlier one.