Shorten the deprecation for export without --resolve.
#19000
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The first release with this deprecation will be 2.16.x, and it really doesn't seem necessary to drag out the deprecation until 2.23.x. Getting rid of this in 2.18.x, at the same time as the tool lockfile changes, will allow us to more aggressively delete a lot of complicated code.
|
I originally set this to 2.23.x but I'm not sure why. I think back then we had conversations about longer deprecation cycles, but this seems excessive even by those standards. And we have related deprecations targeting 2.18.x, so might as well get them all over with. |
kaos
approved these changes
May 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The first release with this deprecation will be 2.16.x, so this isn't a user-facing change yet.
It doesn't seem necessary to drag out the deprecation until 2.23.x. Getting rid of this in 2.18.x,
at the same time as some tool lockfile deprecations expire, will allow us to delete a lot of complicated
code much sooner.