Repository navigation
CI: run the Emulator Preview leg on API 37.1 too - #43
Merged
Merged
Conversation
The preview emulator package (emulators;latest) was exercised against the 37.0 and 37.2 16 KB page-size images only, while the instrumented matrix already covers 37.1. Add the 37.1 image to the preview matrix so the preview binary is tried on every API 37 image the project builds against. The leg is non-blocking like the other preview legs; its artifacts carry the API level in their names, so nothing collides. README rows updated.
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.
Adds the API 37.1
google_apis_ps16kimage to the Emulator Preview matrix, next to 37.0 and 37.2, so theemulators;latestpackage is exercised on every API 37 image this project already builds against in its instrumented matrix. The leg stays non-blocking like the other preview legs and its artifacts carry the API level in their names. README rows updated.Checked locally: the workflow still parses as YAML and the composite action takes the API level as an input, so no mapping was needed.