Update deprecation date from far in the future to 2023 (which is more…#5114
Open
stolky wants to merge 1 commit into
Open
Update deprecation date from far in the future to 2023 (which is more…#5114stolky wants to merge 1 commit into
stolky wants to merge 1 commit into
Conversation
… likely the right date)version for resource access feature deprecation in 2203 seems a bit far in the future this date is likely a typo, and should be 2023 (not that big a deal but a bit sloppy)
Contributor
|
Learn Build status updates of commit ee5a368: ✅ Validation status: passed
For more details, please refer to the build report. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
… likely the right date)version for resource access feature
deprecation in 2203 seems a bit far in the future
this date is likely a typo, and should be 2023
(not that big a deal but a bit sloppy)