Update deprecation message to specify version 2.4.0 not 2.3.2 #265
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
kimpepper
requested review from
VachaShah,
dblock,
harshavamsi,
shyim and
saimedhi
as code owners
shyim
previously approved these changes
Jan 23, 2025
kimpepper
force-pushed
the
update-deprecated-version
branch
from
d0b232f to
09c9b8c
Compare
Signed-off-by: Kim Pepper <[email protected]>
kimpepper
force-pushed
the
update-deprecated-version
branch
from
09c9b8c to
4b0bca3
Compare
shyim
approved these changes
Jan 23, 2025
kimpepper
changed the title
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.
Description
We specified the deprecation version as 2.3.2 in all the recent PRs, however the correct version is 2.4.0.
This PR updates all the deprecation messages.
Issues Resolved
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.