Feature: Allow using custom tracks with google-play
#215
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
|
Codemagic docs on Build versioning need to be updated with some marginal changes once this is live. |
|
Documentation updates are in separate PR #216. |
artemii-yanushevskyi
approved these changes
Apr 12, 2022
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.
The main purpose of this PR is to add support for custom tracks in
google-play get-latest-build-number(addresses isseu #152).Updated actions
google-play get-latest-build-numberNew actions
google-play tracks getgoogle-play tracks listIn order to support custom release tracks predefined track names were removed entirely, and a single request is now made to Google Play API, which returns all tracks, instead of querying each track separately. That way we get access to all available tracks.
Some quite significant changes were applied the codebase in order to get this done nicely in a modular way. Full overview of the changes are documented under the changelog entry.