Uh oh!
There was an error while loading. Please reload this page.
Verify the standalone build on every pull request - #8
Merged
Conversation
Every module is built two ways: inside the android-sdk aggregate build, and on its own. Development happens in the aggregate build, so the standalone side rots silently — it is only exercised when the publish workflow runs, which is to say on release day. Add a `build.yml` that assembles the module on its own for every pull request, so this drift surfaces when the change is made instead of at release time. Where needed this commit also repairs the standalone build itself (missing wrapper/settings, missing version-catalog entries, dependency versions that had drifted from the aggregate build).
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 freeto 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.
Every module is built two ways: inside the android-sdk aggregate build, and on
its own. Development happens in the aggregate build, so the standalone side
rots silently — it is only exercised when the publish workflow runs, which is
to say on release day.
Add a
build.ymlthat assembles the module on its own for every pull request,so this drift surfaces when the change is made instead of at release time.
Where needed this commit also repairs the standalone build itself (missing
wrapper/settings, missing version-catalog entries, dependency versions that had
drifted from the aggregate build).