[Tooling] Fix update_rollouts failing on initial submission (draft -> inProgress)

[AliSoftware]

Why?

During the call to bundle exec fastlane update_rollouts percent:0.2, the lane failed to find the release to update the rollout for in Google Play (See internal discussion in p1733749465871129/1733504114.702699-slack-C028JAG44VD):

This was because of the way the upload_to_play_store action is implemented in fastlane, which only searches for existing releases that are already in inProgress status when it runs the code to update a rollout.

This means that the current fastlane implementation didn't support the possibility to submit an already-existing draft release with an initial rollout. Instead, it was only able to do an initial submission if it was done as part of the initial upload_to_play_store that also uploads the .aab/.apk, and was only able to update the rollout of a release if that release was already inProgress and submitted with a lower rollout—but it was not able to promote an existing draft to inProgress (without doing a new .aab upload and creating a new release).

How?

This PR temporarily points to my fix in the fastlane repo to allow us to call update_rollouts percent:0.2 for a release that already exists in Play Store Console but in draft state.

Once the fix is merged and fastlane ships a new version including it, we shall revert the Gemfile to point back to a ~> x.y version constraint.

Note

I'm targeting the release/7.79 branch so that we can benefit from and validate the fix during this sprint and the 7.79 release process this week.

Testing Instructions

I already tested this by running bundle exec fastlane update_rollouts percent:0.2 from this branch while the 3 Releases (phone, automotive, wear) for the 7.79-rc-1 beta were still in "Draft" status, and confirmed that the fix worked

Checklist

• If this is a user-facing change, I have added an entry in CHANGELOG.md N/A
• Ensure the linter passes (./gradlew spotlessApply to automatically apply formatting/linting)
• I have considered whether it makes sense to add tests for my changes N/A
• All strings that need to be localized are in modules/services/localization/src/main/res/values/strings.xml N/A
• Any jetpack compose components I added or changed are covered by compose previews N/A
• I have updated (or requested that someone edit) the spreadsheet to reflect any new or changed analytics. N/A

[dangermattic]

	1 Message
📖	This PR is still a Draft: some checks will be skipped.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in 📱 Mobile by scanning the QR code below to install the corresponding build.

	App Name	📱 Mobile
	Build Type	debugProd
	Commit	6ca16c9
	Direct Download	pocketcasts-app-prototype-build-pr3341-6ca16c9.apk

📲 You can test the changes from this Pull Request in 🚗 Automotive by scanning the QR code below to install the corresponding build.

	App Name	🚗 Automotive
	Build Type	debugProd
	Commit	6ca16c9
	Direct Download	pocketcasts-automotive-prototype-build-pr3341-6ca16c9.apk

📲 You can test the changes from this Pull Request in ⌚ Wear by scanning the QR code below to install the corresponding build.

	App Name	⌚ Wear
	Build Type	debugProd
	Commit	6ca16c9
	Direct Download	pocketcasts-wear-prototype-build-pr3341-6ca16c9.apk

[mebarbosa]

Thanks for putting this PR! The drafted was published in beta now like you said