Steps Google Play Deploy Versions Save

What's Changed

• Increased retries by @lpusok in https://github.com/bitrise-steplib/steps-google-play-deploy/pull/155

Full Changelog: https://github.com/bitrise-steplib/steps-google-play-deploy/compare/3.7.4...3.7.5

What's Changed

• Retry on http status unauthorized by @lpusok in https://github.com/bitrise-steplib/steps-google-play-deploy/pull/152

Full Changelog: https://github.com/bitrise-steplib/steps-google-play-deploy/compare/3.7.3...3.7.4

What's Changed

• Print suggestion when API returns internal server error by @ofalvai in https://github.com/bitrise-steplib/steps-google-play-deploy/pull/143
• Apply YAML lint by @ofalvai in https://github.com/bitrise-steplib/steps-google-play-deploy/pull/138
• Use newer signature scheme in E2E tests by @ofalvai in https://github.com/bitrise-steplib/steps-google-play-deploy/pull/139

Full Changelog: https://github.com/bitrise-steplib/steps-google-play-deploy/compare/3.7.2...3.7.3

[#133] Step description update

[#131] Print available Google Play release tracks to log

🥇 Thank you @bartwesselink for the contribution!

(#126) Support uploading multiple mapping.txt files along multiple APKs or AABs. The step input mapping_file now accepts a | or \n separated list of mapping file paths. Please note that the mapping file order should match the order of APK/AAB paths.

New step input: Acknowledge Bundle Installation Warning (ack_bundle_installation_warning).

• Must be set to true if the App Bundle installation may trigger a warning on user devices (for example, if installation size may be over a threshold, typically 100 MB). In those cases, uploading an AAB to Google Play will result in an error which you can accept by setting this input to true.
• Default: false.

• Introduced a new input retry_without_sending_to_review to signal that the step should retry sending changes by setting the newly introduced changesNotSentForReview flag. #119 #120
• The changes are first always sent without the flag, but if it fails it can be retried by applying the flag. Please not that in later case the review has to be manually initiated on the Google Play Console UI

• The status of the release can now set via the Status input parameter (#116).
• The input is optional to preserve backward compatibility, so if it is not set, the status of the release is calculated as in the past (based on the value of the User Fraction input).
• Based on the Google API documentation, the User Fraction input is only applied if the status of the release is inProgress or halted.
• You may see the supported statuses here.

Update dependencies