Split the sequential deploy-playstore job into two parallel jobs: deploy-playstore (Play Store only) and deploy-apk (APK server deploy). Both use the same Dagger remote engine cache, so the second job hits cached Android toolchain layers — wall-clock drops from T_publish + T_deploy_apk to max(T_publish, T_deploy_apk).
Reduced fetch-depth from 50 to 1 in all jobs — CI never needs git history (changelog generation is a local task, not a CI step; git rev-parse --short HEAD works with depth 1).
Updated publish-website.needs and label-deploy-health.needs to include the new deploy-apk job so downstream jobs still wait for everything.
Test plan
Verify deploy-playstore job no longer contains the APK deploy step
Verify new deploy-apk job runs in parallel with deploy-playstore and build-linux
Verify publish-website waits for all three parallel jobs before running
Verify label-deploy-health waits for all four jobs before updating
## Summary
- Split the sequential `deploy-playstore` job into two parallel jobs: `deploy-playstore` (Play Store only) and `deploy-apk` (APK server deploy). Both use the same Dagger remote engine cache, so the second job hits cached Android toolchain layers — wall-clock drops from `T_publish + T_deploy_apk` to `max(T_publish, T_deploy_apk)`.
- Reduced `fetch-depth` from 50 to 1 in all jobs — CI never needs git history (changelog generation is a local `task`, not a CI step; `git rev-parse --short HEAD` works with depth 1).
- Updated `publish-website.needs` and `label-deploy-health.needs` to include the new `deploy-apk` job so downstream jobs still wait for everything.
## Test plan
- [ ] Verify `deploy-playstore` job no longer contains the APK deploy step
- [ ] Verify new `deploy-apk` job runs in parallel with `deploy-playstore` and `build-linux`
- [ ] Verify `publish-website` waits for all three parallel jobs before running
- [ ] Verify `label-deploy-health` waits for all four jobs before updating
Fixes #171
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
deploy-playstorejob into two parallel jobs:deploy-playstore(Play Store only) anddeploy-apk(APK server deploy). Both use the same Dagger remote engine cache, so the second job hits cached Android toolchain layers — wall-clock drops fromT_publish + T_deploy_apktomax(T_publish, T_deploy_apk).fetch-depthfrom 50 to 1 in all jobs — CI never needs git history (changelog generation is a localtask, not a CI step;git rev-parse --short HEADworks with depth 1).publish-website.needsandlabel-deploy-health.needsto include the newdeploy-apkjob so downstream jobs still wait for everything.Test plan
deploy-playstorejob no longer contains the APK deploy stepdeploy-apkjob runs in parallel withdeploy-playstoreandbuild-linuxpublish-websitewaits for all three parallel jobs before runninglabel-deploy-healthwaits for all four jobs before updatingFixes #171