Repository navigation
Release: put the APKs on the CDN and update the admin panel - #74
Merged
Merged
Conversation
A new admin job, after the Android build, uploads the arm64 and armv7 APKs to R2 through the backend's release routes, replaces the old builds on the download page, and points the in-app updater at the new arm64 APK. Only version, downloadUrl and releaseNotes change on the updater row; minVersion, forceUpdate and active stay as set in the admin panel. The `admin` input (publish | skip) turns it off, and `release: skip` skips it too. Without SOZO_MOBILE_RELEASE_TOKEN it warns and does nothing. Telegram says whether the CDN and updater were updated.
Stable moved to 3.50.0, which needs Gradle 9.3.1 (the project has 8.14) and fails to compile the liquid_glass shader, so test, build-android and build-linux all failed on unchanged app code. The release workflow had the same unpinned setup.
ubuntu-latest became 26.04, whose clang turns a deprecated-literal-operator warning in flutter_secure_storage_linux's json.hpp into an error under the plugin's -Werror.
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
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.
New
adminjob inrelease.yml, right after the Android build (runs in parallel with the desktop builds):arm64andarmv7APKs to R2 viaPOST /admin/downloads/upload-url+ presigned PUT.replacePrevious: true, so the old builds disappear from the page./admin/app-versions/android) at the new arm64 APK:version= build number,downloadUrl,releaseNotes(thenotesinput, orSozo v<version>).minVersion,forceUpdateandactiveare kept as set in the admin panel.New dispatch input
admin: publish | skip(default publish).release: skipalso skips it. Tag pushes publish.Needs backend professorDeveloper/sozo-backend
ci/mobile-release-tokenmerged and deployed, and theSOZO_MOBILE_RELEASE_TOKENsecret in this repo. Without the secret the job only warns.CI fixes (unrelated to the above, but they broke every build):
ci.ymlandrelease.yml. Stable moved to 3.50.0, which needs Gradle 9.3.1 (project has 8.14) and fails on the liquid_glass shaders.ubuntu-24.04.ubuntu-latestbecame 26.04, whose clang failsflutter_secure_storage_linuxunder-Werror.