[Backport 2.0] Add 1.3.2 version to main causing gradle check failures#2684
Merged
[Backport 2.0] Add 1.3.2 version to main causing gradle check failures#2684
Conversation
Member
|
@dreamer-89 I think this needs a manual backport/amend for DCO, not sure what the problem is. |
0f2e394 to
7f022a2
Compare
Signed-off-by: Suraj Singh <surajrider@gmail.com> (cherry picked from commit e051a42) Add 1.3.2 to 2.0 branch Signed-off-by: Suraj Singh <surajrider@gmail.com>
7f022a2 to
d5ef205
Compare
Collaborator
|
❌ Gradle Check failure 0f2e394ffa96a838e814d729fcfd856bbdfdb77d |
Collaborator
|
❌ Gradle Check failure 7f022a280ec730fb518c09d9bb6434d3ee8ff8a0 |
nknize
approved these changes
Mar 31, 2022
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
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.
Backport e051a42 from #2679