Improve update-for-v9 reminders from get-aliases#102336
Merged
DaveCTurner merged 1 commit intoelastic:mainfrom Nov 20, 2023
Merged
Improve update-for-v9 reminders from get-aliases#102336DaveCTurner merged 1 commit intoelastic:mainfrom
DaveCTurner merged 1 commit intoelastic:mainfrom
Conversation
In elastic#101815 we made some changes to the get-aliases API that need followup actions when preparing to release v9. At the time they were marked with a transport version that will become obsolete in v9, but with elastic#101767 we now have a better mechanism for leaving a reminder for this kind of action. This commit updates things to use the new @UpdateForV9 annotation instead.
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
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
3 participants
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.
In #101815 we made some changes to the get-aliases API that need
followup actions when preparing to release v9. At the time they were
marked with a transport version that will become obsolete in v9, but
with #101767 we now have a better mechanism for leaving a reminder for
this kind of action. This commit updates things to use the new
@UpdateForV9annotation instead.