Codegen feature-branch: make stability and deprecation independent properties (#244)#280
Merged
jsuereth merged 1 commit intoFeb 29, 2024
Conversation
lmolkova
changed the title
jsuereth
approved these changes
Feb 29, 2024
lmolkova
pushed a commit
to lmolkova/build-tools
that referenced
this pull request
Mar 7, 2024
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
2 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.
Bring stability/deprecation PR #244 into codegen feature- branch based on @jack-berg request here #244 (comment)
This is cherry-pick + conflict resolution, nothing else.
Rebasing from main brings all the other breaking changes wrt stability, which won't help Java validate codegen.