fix: trigger deploy on script changes, add changelog dep, deepen fetch (#228) #233

Merged
guettlibot merged 1 commits from issue-228-fix into main 2026-05-24 19:05:16 +00:00
guettlibot commented 2026-05-24 19:04:44 +00:00 (Migrated from codeberg.org)

Changes

  • deploy.yml: Add scripts/deploy_playstore.py to android_re change-detection regex so upload-script fixes trigger a redeploy automatically (Root Cause 2)
  • deploy.yml: Change fetch-depth: 1fetch-depth: 100 in the deploy-playstore job so git log -n 50 produces a full changelog (Root Cause 3, secondary blocker)
  • Taskfile.yml: Add deps: [generate-changelog] to publish-android task so assets/changelog.txt is regenerated before every Play Store build (Root Cause 3)

Open questions filed

  • #229 — Should other deploy jobs also use fetch-depth > 1?
  • #230 — Is fetch-depth: 100 sufficient or should we use full history?
  • #231 — Should assets/changelog.txt be gitignored since CI regenerates it?
  • #232 — Is the one-commit changelog lag acceptable?

Fixes #228

## Changes - **deploy.yml**: Add `scripts/deploy_playstore.py` to `android_re` change-detection regex so upload-script fixes trigger a redeploy automatically (Root Cause 2) - **deploy.yml**: Change `fetch-depth: 1` → `fetch-depth: 100` in the `deploy-playstore` job so `git log -n 50` produces a full changelog (Root Cause 3, secondary blocker) - **Taskfile.yml**: Add `deps: [generate-changelog]` to `publish-android` task so `assets/changelog.txt` is regenerated before every Play Store build (Root Cause 3) ## Open questions filed - #229 — Should other deploy jobs also use fetch-depth > 1? - #230 — Is fetch-depth: 100 sufficient or should we use full history? - #231 — Should assets/changelog.txt be gitignored since CI regenerates it? - #232 — Is the one-commit changelog lag acceptable? Fixes #228
Sign in to join this conversation.