The committed gradle-wrapper.jar was the real 8.11.1 wrapper jar nested
inside another jar, without the org/gradle/cli classes, so ./gradlew failed
everywhere with NoClassDefFoundError: org/gradle/cli/CommandLineParser
(CI was the first place it ran from a fresh checkout). gradlew was a
hand-written launcher and gradlew.bat, which the dev guide tells Windows users
to run, did not exist.
Regenerated with `gradle wrapper --gradle-version 8.11.1` from the official
distribution (sha256 f397b287…, matching services.gradle.org); the jar matches
the published gradle-8.11.1-wrapper.jar.sha256 (2db75c40…). The distribution
URL is unchanged. .gitattributes pins gradlew to LF and *.bat to CRLF.
The UI review job starts its media fixture through server/node_modules/tsx,
so it installs the server's dependencies too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- main is the long-lived development branch: release.yml no longer runs on
a push to it, only on v* tags and workflow_dispatch. ci.yml now runs on
every branch push, main included.
- android-actions/setup-android's default package list includes `tools`,
which current command-line tools no longer carry, so sdkmanager failed;
install exactly platform-tools, android-35 and build-tools 35.0.1.
- reader-chrome.test.ts left its React roots mounted; a scheduled commit
could land after jsdom teardown and fail the run with an unhandled
"Right-hand side of 'instanceof' is not an object" (all tests passing).
Unmount in afterEach.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ci.yml (PRs, non-main pushes, and called by release.yml):
- server: typecheck, test, build
- web: typecheck, test (with server deps, for search parity), build
- UI review: production bundle in Playwright's Chromium, screenshots kept
- Android: shell contract check, web assets staged and verified, debug APK
release.yml (main, v* tags, manual):
- runs CI first; nothing is published from a red build
- builds hectorqin/reader-pro for linux/amd64 and linux/arm64 on native
runners (no QEMU), pushes by digest, then one job creates the multi-arch
tags: main + sha-<short> for main; x.y.z, x.y, latest + sha for tags
- needs DOCKERHUB_USERNAME and DOCKERHUB_TOKEN repository secrets
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>