Skip to content

Conversation

vtjnash
Copy link
Member

@vtjnash vtjnash commented Oct 6, 2025

Without this, we would never be permitted to remove this deprecation,
which would have been self-defeating. Make sure to warn if the answer
would eventually change (from true->false).

Without this, we would never be permitted to remove this deprecation,
which would have been self-defeating. Make sure to warn if the answer
would eventually change (from true->false).
@vtjnash vtjnash added the backport 1.12 Change should be backported to release-1.12 label Oct 6, 2025
@Keno
Copy link
Member

Keno commented Oct 7, 2025

This was deliberate and discussed extensively. If you want to change this, I think there needs to be a stronger argument than currently presented.

@vtjnash vtjnash removed the backport 1.12 Change should be backported to release-1.12 label Oct 8, 2025
@vtjnash
Copy link
Member Author

vtjnash commented Oct 14, 2025

Okay, I'm fine with never removing the backdating code, and v1.12 is released, so changing it yet again now would be breaking anyways

@vtjnash vtjnash closed this Oct 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants