Update 'for removal' versions > 3.5.0 to 4.0.0 #44964
Closed
Conversation
This file contains hidden or 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
Signed-off-by: Shivam Thorat <[email protected]>
shivammm21
force-pushed
the
update-deprecation-removal-versions-44959
branch
from
f548476 to
52b3310
Compare
spring-projects-issues
added
the
status: waiting-for-triage
|
Thanks for the PR, @shivammm21, but once again this issue is already assigned to someone else so we won't accept a contribution. To avoid wasted effort, I'd recommend commenting on an unassigned issue to indicate that you'd like to contribute. If it's an issue that's suitable for contribution, the issue can then be assigned to you and you can start working on it. |
wilkinsona
added
status: declined
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.
Fixes #44959
Since 3.5.x is the last 3x generation, this PR updates all our deprecation removal versions from >3.5.0 (like 3.6.0, 3.7.0, etc.) to 4.0.0. This ensures a consistent deprecation timeline with no scheduled removals in versions that won't exist.
The updates are only to JavaDoc comments, not to the actual code or @deprecated annotations, which don't contain version-specific removal information.