You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SKILL.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,12 @@ Follow this workflow when the user asks to deploy SSUTime.
34
34
- Increase the hardcoded `versionName` by one patch step unless the user specified a version. Example: `1.0.7` -> `1.0.8`.
35
35
- Use the bumped `versionName` as the GitHub Release tag with a `v` prefix, for example `v1.0.7`.
36
36
- Do not rely on CI to derive app versions from the GitHub Release tag; the Play build uses the committed Gradle version.
37
-
4. Run checks:
37
+
4. Set the Play in-app update priority before the final release commit:
38
+
- Inspect the release changes and commits to decide whether they include an LMS API version change. Treat changes to the `libs.lms` dependency version, LMS API client compatibility code, or other LMS API version migration work as an LMS API version change.
39
+
- If the release includes an LMS API version change, set `.github/workflows/google-play-production.yml``inAppUpdatePriority` to `5` so the app's immediate in-app update flow can run for that version.
40
+
- For all other releases, set `.github/workflows/google-play-production.yml``inAppUpdatePriority` to a low value such as `0`; do not leave it at `4` or `5`, because that would trigger the app's immediate update prompt.
41
+
- Commit and push the workflow priority value together with the version bump and release changes. The GitHub Release workflow uses the committed workflow file, so this value must be correct before creating the GitHub Release.
42
+
5. Run checks:
38
43
39
44
```bash
40
45
./gradlew test :app:compileReleaseKotlin :app:bundleRelease :app:assembleRelease
0 commit comments