ci(build-tauri): fail fast if aw-server-rust submodule is on an older release line - #1391
Conversation
…g in build-tauri Adds a fast-fail step in build-tauri that reads the bundled aw-server version from aw-server-rust/aw-server/Cargo.toml and compares the major.minor prefix against the AW release tag. If the submodule is pinned to an older release line, the build fails immediately rather than producing a 30-min Tauri bundle with the wrong backend (the Windows 0.14 release shipped with aw-server v0.13.1 due to this). Fixes ActivityWatch#1380
Greptile SummaryThe PR extends the existing release-line validation to Tauri builds, addressing the previously reported bypass.
Confidence Score: 5/5The PR appears safe to merge. The previously reported Tauri bypass is fixed: every Tauri matrix target now performs the version check after checkout and version initialization, and no blocking failure remains. Important Files Changed
Reviews (2): Last reviewed commit: "ci(build-tauri): add missing aw-server-r..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| - name: Verify aw-server-rust submodule version matches release tag | ||
| if: startsWith(github.ref, 'refs/tags/v') |
There was a problem hiding this comment.
When a release tag pins aw-server-rust to a different release line, only the independent Qt job runs this check, so all five Tauri matrix jobs continue building the mismatched bundle instead of failing before the expensive build steps.
Knowledge Base Used: Packaging and release pipeline
The version-freshness check landed in build-qt but not build-tauri — the job that actually shipped the mismatched bundle in ActivityWatch#1380. Add the same fail-fast step to build-tauri so all five Tauri matrix jobs are guarded, not just the independent Qt build.
|
Good catch from Greptile — the version guard only landed in |
|
@greptileai review |
1 participant
Fixes #1380 — adds a pre-build version match check in the build-tauri job.