# Google Play Deploy v3.3.0 **URL:** \ **Category:** Changelog\ **Created:** [March 23, 2021, 3:06pm UTC](https://discuss.bitrise.io/t/google-play-deploy-v3-3-0/16260 "2021-03-23T15:06:13Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\ **Post date:** [March 23, 2021, 3:06pm UTC](https://discuss.bitrise.io/t/google-play-deploy-v3-3-0/16260/1 "2021-03-23T15:06:13Z")
- 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](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#release), the `User Fraction` input is only applied if the status of the release is `inProgress` or `halted`. - You may see the supported statuses [here](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#status). > **[Release 3.3.0 ยท bitrise-steplib/steps-google-play-deploy](https://github.com/bitrise-steplib/steps-google-play-deploy/releases/3.3.0)** > > 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 a... ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\ **Post date:** [June 23, 2021, 3:04pm UTC](https://discuss.bitrise.io/t/google-play-deploy-v3-3-0/16260/2 "2021-06-23T15:04:31Z")
This topic was automatically closed after 91 days. New replies are no longer allowed.