Fix API warning task #138
Merged
Fix API warning task #138
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
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.
Per b/338644141,
This fixes the
warnAboutAPIChangestask that was failing when one of the projects didn't have any changes. This was due to an oversight in how Gradle propagates skipped properties. We've ran into this before, but it's easy to forget that even if a task is skipped- Gradle still considers outputs to be valid (even if they don't exist). So mapping against it doesn't provide the expected behavior. You can read more about this on their repo: /gradle/issues/7442This PR also fixes the following: