Releases and changelog

Release status — 20 October 2026: Squire 1.0.0-beta.1, including the coach Android app, is published and accepted for beta evaluation. Packaging/signature checks passed, the founder accepted the Galaxy S20+ standalone field/offline walkthrough, and the uploaded Android bundle's APK checksum matches the recorded build. Broader device, accessibility and historical-upgrade coverage are follow-up work, not unfinished beta.1 release gates. Institutions still approve their own environment and privacy/security arrangements before using real athlete data.

Published releases

The panel reports actual GitHub releases. A source tag is available for Squire 1.0.0-beta.1; it does not itself provide an APK download or promise stable support. Stable Squire 1.0.0 has no announced date.

Squire 1.0.0-beta.1 — 19 October 2026

The university implementation is on main. The existing source tag v1.0.0-beta.1 identifies an earlier candidate and does not yet identify the APK build containing the later offline fixes. It includes institution-owned deployment, role-specific workspaces, instance branding, staff plan/event browsing and the coach Android field workflow. Read the canonical changelog for the full history.

The signed Android APK build and signature checks passed. An isolated Android 14 emulator started offline without Metro and preserved pending attendance plus an unsubmitted score draft through a controlled versionCode update. Reconnecting confirmed attendance, one score result and event completion. The qualification baseline used the same production code with a lower versionCode and the same key; this does not establish historical release/schema migration or physical-device acceptance. The initial beta APK showed a stale offline error after successful sync. The fix is merged; its source checks pass, and the founder subsequently reported the first S20+ walkthrough passed on 20 October. See evidence and limits.

Squire 1.0.0-beta.2 — release preparation

The sports and coaching foundation and its review fixes are accepted and merged in application PR #135. Squire 1.0.0-beta.2 release metadata and signed packaging are being prepared in PR #138. Beta.1 remains the published download until the new GitHub prerelease exists.

It adds:

• institution sports and coaching specialties;
• primary and supporting coaches;
• concurrent goal-specific plans with explicit replace and end;
• staff athlete profiles;
• coach-recorded sessions with attributed correction history.

Read the roles, administration, programs and limitations guides, and the source changelog.

Installation and upgrades

Follow the Android build and upgrade guide: retain the private signing key, install signed updates in place and verify saved work through an actual upgrade. Server operators must back up PostgreSQL and private files together before forward migrations. Do not reset or reseed an existing institution.

Broader physical-device coverage, accessibility, native recovery and production operations still require evaluation. Use synthetic records until the institution approves real athlete data. Provider validation and first-user field feedback remain backlog items.

Physical evaluation and signing ownership

See the phone guide for the updated signing-backup and USB-connected S20+ evaluation procedure, coach-only native scope and offline privacy/sync boundaries. Those instructions accompany merged fixes; the first S20+ walkthrough is now reported passed, with broader coverage separate.

Whole-product evaluation and downloads

The 19 October review considers Rafik suitable for a technically supported, self-hosted evaluation beta with synthetic records. A fresh production web build and expanded local documentation checks passed. First-user feedback and optional cloud validation remain backlog items. Institution privacy/security, Unix recovery/rollback and alert delivery remain separate before live athlete data.

The current readiness record accompanies documentation PR #127; it does not retag the original source or publish an updated package. The newer APK has package/signature evidence; the founder subsequently reported the S20+ walkthrough passed. The founder reports the signing keys backed up with 7-Zip to PC and cloud storage; this is owner confirmation, not an independently inspected backup/restore.

Keep downloads on GitHub Releases and link exact versioned assets from this website. GitHub source ZIP/tar.gz archives contain source, not a database backup or prebuilt installer. The published bundle includes matching checksum/build metadata. The uploaded Android bundle is linked below.

Published beta and phone result — 20 October 2026

On 20 October 2026, the founder reported that the instructed Galaxy S20+ standalone installation and field/offline-recovery walkthrough worked as intended. This is a successful owner-reported physical-phone check. Android version, the installed APK checksum and per-locale/accessibility results were not supplied; broader device, tablet, accessibility and historical-upgrade coverage remain separate. See the recorded phone result and application PR #136.

The official Android download bundle is now published on the beta.1 GitHub prerelease. Extract the ZIP and open 1.0.0-beta.1/Rafik-Squire-1.0.0-beta.1-android.apk. It includes SHA256SUMS and non-secret build.json. On 20 October, the downloaded APK's computed SHA-256 matched both bundled records and the existing package receipt: 1654e44fd6f324d2403984a6a880b3dffabf81f3615c9ac8a71c5992a417fb5e. Its source is 5d1ce761505b07272c6d5b43414cd1d754b41517; the source archive tag remains 4ac70c8. No rebuild, tag move or repeat phone test was needed.

Completing beta.1 Android downloads

The accepted Android bundle is published and its APK checksum is verified. Keep the existing source tag and signing key intact. See install/build guidance; broader device/accessibility and historical-upgrade evidence remain separate.

Beta.2 upgrade notes

Back up PostgreSQL and private files together before applying the four forward migrations (202610191200 through 202610191500). Existing assigned coaches become primary links; existing plans and history remain. Do not reset or reseed. See the candidate upgrade guide.

Android beta.2 uses versionCode 1000002 and the existing signing identity. Install its signed APK as an update, never uninstall or clear saved work. Beta.1 phone acceptance is complete; no beta.1-to-beta.2 upgrade result is claimed yet. The API contract version is independent; delegated workout logging remains web-only.

Release tracking: Release Beta.2. The release panel above lists actual published downloads; this documentation does not create a release.