-
-
Notifications
You must be signed in to change notification settings - Fork 252
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
manually bump to 19.0.0 Alpha 02 #3733
Conversation
there seems to be something wrong that alpha workflow did not update the apps version. Thats why gplay complains with "Google Api Error: forbidden: Cannot update a published APK. - Cannot update a published APK." because it always tries to upload 19.0.0 Alpha 02. On nextcloud ftp server, it was most probably always overwritten as there is an up to date alpha2 version. Seeting the version number to 19.0.0 Alpha 02 should make sure that an alpha 3 is built on next automation run. The root cause that the version was/is not changed by the automation is still unclear. Signed-off-by: Marcel Hibbe <[email protected]>
APK file: https://www.kaminsky.me/nc-dev/android-artifacts/3733-talk.apk |
manual trigger of alpha automation unveiled that push fails because of "Commits must have verified signatures":
So Alpha3 is published on gplay and ftp, but problem with verified signatures / push has to be solved for next run. |
manual bump because alpha automation failed to bump version because of "Commits must have verified signatures". See #3733 (comment) Signed-off-by: Marcel Hibbe <[email protected]>
still because of #3733 Signed-off-by: Marcel Hibbe <[email protected]>
still because of #3733 Signed-off-by: Marcel Hibbe <[email protected]>
still because of #3733 Signed-off-by: Marcel Hibbe <[email protected]>
reason was that the bot had not enough permissions for the repository to push directly to master. |
there seems to be something wrong that alpha workflow did not update the apps version. Thats why gplay complains with
"Google Api Error: forbidden: Cannot update a published APK. - Cannot update a published APK." because it always tries to upload 19.0.0 Alpha 02.
On nextcloud ftp server, it was most probably always overwritten as there is an up to date alpha2 version.
Seeting the version number to 19.0.0 Alpha 02 should make sure that an alpha 3 is built on next automation run.
The root cause that the version was/is not changed by the automation is still unclear.
🏁 Checklist
/backport to stable-xx.x