ci(release): check for existing versionCode on Google Play before build #3320
Conversation
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
Adds a new `check-versioncode-google-play` job to the release workflow. This job uses Fastlane to verify if the current `versionCode` already exists on the Google Play internal track before proceeding with a build and deploy. The `release-google` and `release-fdroid` jobs are now conditional on this check: - If the `versionCode` does not exist, the internal build and upload to Google Play and F-Droid proceeds as normal. - If the `versionCode` already exists on an internal release, the build and upload steps are skipped to prevent failures, but promotion logic can still run. - When promoting to beta or production, the workflow now fails if the `versionCode` is not found on the internal track, preventing promotion errors. Signed-off-by: James Rich <[email protected]>
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 a new
check-versioncode-google-playjob to the release workflow. This job uses Fastlane to verify if the currentversionCodealready exists on the Google Play internal track before proceeding with a build and deploy.The
release-googleandrelease-fdroidjobs are now conditional on this check:versionCodedoes not exist, the internal build and upload to Google Play and F-Droid proceeds as normal.versionCodealready exists on an internal release, the build and upload steps are skipped to prevent failures, but promotion logic can still run.versionCodeis not found on the internal track, preventing promotion errors.