reply
"retired" is probably a followup to functionality that was "deprecated".
I agree "breaking" would be clearer
It's a holdover from previous posts where there were more clearly defined deprecations.
but yes, in this case it's more of a behavioural change of defaults, so they just picked the closest vaguely mapped retired/deprecations tag.
1: https://github.blog/changelog/?type=deprecations