Notes on how to release changes.
Last updated 2023/08/29
- Verify the continous deployment github-action is working. It should auto-publish the changes. https://github.com/erosson/freecbt/actions/workflows/deploy.yml
- That is, do nothing: the master branch is auto-published.
- You can also manually run
yarn deploy
Releasing a new build with big updates/that requires a new appstore deployment
- In
app.json
, incrementexpo.android.versionCode
,expo.ios.buildNumber
, andexpo.version
as needed. - Push your changes to the
appstore-build
git branch. The CI robot will build and publish everything there to the app stores. - Visit the app store websites, test manually, and launch.
- Follow the
apk
steps below; the automation there is broken
relevant documentation: https://docs.expo.dev/submit/introduction/
- android
- increment
expo.android.versionCode
inapp.json
. submit to git. do this before building yarn buildsubmit:android
to build + upload to play console- or
yarn build:android
+yarn submit:android
, for separate steps
- or
- https://play.google.com/console/
- requires api key, service account. relevant docs: https://github.com/expo/fyi/blob/main/creating-google-service-account.md
- increment
- ios
yarn buildsubmit:ios
to build + upload to play console- or
yarn build:ios
+yarn submit:ios
, for separate steps submit
replaces my old macincloud shenanigans. Thanks Expo!
- or
- result at https://appstoreconnect.apple.com/apps/1516063390/testflight/ios - manually test and launch
- requires api key. relevant auth docs: https://github.com/expo/fyi/blob/main/creating-asc-api-key.md
- android apk (non-appstore)
yarn build:apk
- Upload to the releases page. https://github.com/erosson/freecbt/releases
- There's a github-action that should automate this, but it's been broken for a while (since our big expo 47 update). https://github.com/erosson/freecbt/blob/master/.github/workflows/apk.yml