Fixed issues with Build files for Android and Linux

2026-09-01 15:24:41 +02:00
parent f98f4521c2
commit 2751bd8b4c
3 changed files with 37 additions and 14 deletions
@@ -44,6 +44,7 @@ Widget tests run against a mocked backend: build a `MockClient` that answers by

 Notes that are easy to get wrong:

+- **The act-runner of the gitea instance only supports actions up to `node20`.** Anything newer fails with `The runs.using key in action.yml must be one of: [...], got node24`, which is why the Flutter sdk is unpacked from the official archive instead of through `subosito/flutter-action` (that one caches through `actions/cache@v5`). Check the `runs.using` of an action before adding it.
 - The Flutter version is pinned in three places (`FLUTTER_VERSION` in both build workflows, `ARG FLUTTER_VERSION` in `ac_web/Dockerfile`) and must be kept in sync.
 - Steps run with `working-directory: ac_web`, but `upload-artifact` paths are relative to the repository root.
 - The workflows are read from the tag the release points at, so they have to be committed **before** the release is created.