-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GooglePlayRelease@4 replaces GooglePlayRelease@3 and GooglePlayReleaseBundle@3 #304
Comments
I am using GooglePlayRelease@3 for my app release, I saw the warning I tried to use GooglePlayRelease@4 but got this error my current version is 3.194.0 but i don't how to upgrade for 4.x.x and one more thing if i upgrade to 4.x.x will all the service connections will be deleted related to 3.x.x version as i have at least 10 production pipeline |
Hi @tyagirajnish! You can't access the GooglePlayRelease@4 task yet, we're planning to release it today. Please wait until the extension self-updates to version 4.195.0 and then try again.
No, your service connections won't be deleted. You can use the service connections related to 3.x.x in 4.x.x version of the task. |
Thanks for the update @DaniilShmelev, one last thing do I need to update my pipeline once the update is done for the google play release task, if it is automatically updated 3.x.x to 4.x.x then I guess GooglePlayRelease@3 is no longer working |
@tyagirajnish if you had GooglePlayRelease@3 task available in your organization before, you will still have access to it. So, you will be able to choose between V3 and V4 tasks. |
Hi, Is there Closed testing support in v4? I cannot see it. it will be nice to have it beside Beta/Alpha/Internal/Production |
Hi @DaniilShmelev, just a note. The changelog link in your description of this issue appears to be for an edit of the doc, and this redirects me to the main github page. Could you please look to update it to the correct page? |
General Information
Question, Bug, or Feature: Feature
Enter Task Name: GooglePlayRelease@3, GooglePlayReleaseBundle@3, GooglePlayRelease@4
Issue Description
In extension release 4.195.0, GooglePlayRelease@3 and GooglePlayReleaseBundle@3 have been deprecated and removed. GooglePlayRelease@4 task has been added instead.
You will retain access to GooglePlayRelease@3 and GooglePlayReleaseBundle@3 if you had 3.x.x version of the extension installed previously. These tasks won't be removed from your organization on update.
Error logs
You will see the following message if you try to run V3 tasks
##[warning]This task is deprecated. Please switch to GooglePlayRelease@4 that will be released in extension version 3.195.0. You can find a migration guide here: https://github.com/microsoft/google-play-vsts-extension/blob/master/docs/google-play-release-migration.md.
Troubleshooting
It's recommended to migrate from V3 tasks to GooglePlayRelease@4
You may find a migration guide here.
Also take a look at the release changelog here.
The text was updated successfully, but these errors were encountered: