How to read this page Each entry preserves release-time guidance. Earlier-version upgrade steps are historical, not a replacement for the current web-update or kiosk guide.

v1.0.3

Community telemetry retirement

Removes usage reporting and its setup/settings controls. Older privacy requests remain compatible with telemetry disabled. Existing migrations and backup fields remain unchanged.

Private controller templates support an independently fixed database name for reviewed installation renames. Upgrade web components through the backup-first update flow; an installed v1.0.2 kiosk can remain on that version.

Read v1.0.3 release notes.

v1.0.2

Reliable Community Edition updates

Repairs authenticated update claiming and the Pages executor command. Concurrent starts retain one dispatch and audit history. No new migrations, dependencies or permissions.

v1.0.2 is immutable historical release context. Verify each installation's web and physical-kiosk update outcome independently. Read the v1.0.2 release notes for historical verification limits.

v0.24.2

Reliable web update bridge

Repairs authenticated update claiming and the Pages executor command. Concurrent starts retain one dispatch and audit history. No new migrations, dependencies or permissions.

This is historical bridge context for the completed 1.0.2 migration, not a new-installation procedure. Read the v0.24.2 release notes for its release-time limits.

v1.0.1

Worker-compatible Community Edition updates

Corrects the Worker runtime defect that prevented web update preparation in v0.24.0 and v1.0.0. Credentials stay on the fixed GitHub host; unexpected redirects are rejected. Polling cadence is unchanged.

v1.0.1 remains immutable historical release context. Read the v1.0.1 release notes for its verification and recovery limits.

v0.24.1

Worker-compatible web update bridge

Corrects the Worker runtime defect that prevented web update preparation in v0.24.0 and v1.0.0. Credentials stay on the fixed GitHub host; unexpected redirects are rejected. Polling cadence is unchanged.

This corrective bridge predates the completed 1.0.2 migration. Read the v0.24.1 release notes for its historical verification and recovery limits.

v0.10.2

Readability improvements across dashboard and kiosk

This patch makes the day-to-day dashboard, attendance kiosk, and protected fingerprint-maintenance tools easier to read at normal working distance.

Before upgradingNo data migration or configuration update is required. Download an Entire installation backup, manually upgrade the private deployment to the latest stable release, then run the matching Pi installer when you want the kiosk typography update.

Read complete v0.10.2 notes

v0.10.1

Pi desktop kiosk relaunch shortcut

This patch adds a desktop shortcut for reopening the local attendance screen full-screen when a Pi is sitting at the desktop.

Before upgradingThis is a small kiosk installer patch. Existing v0.10.0 deployments can keep running; use it for fresh Pi installs or when you want the desktop relaunch shortcut created by the installer.

Read complete v0.10.1 notes

v0.10.0

Physical kiosk restoration and meeting workflow cleanup

The physical kiosk now more closely matches the pre-community appliance, fingerprint enrollment is touch-first again, and meeting creation/deletion handles the everyday schedule flow with less ceremony.

Before upgradingDownload an Entire installation backup. Manually upgrade the private deployment first, then run the matching v0.10.0 guided installer or staged kiosk update on the Pi. One-click kiosk self-update remains intentionally gated.

Read complete v0.10.0 notes

v0.9.0

Unattended kiosk operations

The physical kiosk now runs as a continuous member-facing scanner, chooses the eligible meeting automatically, and keeps protected maintenance and recovery out of the normal attendance screen.

Before upgradingDownload an Entire installation backup and review meetings for overlaps. Manually upgrade the private deployment first, then run the matching v0.9.0 guided installer on the Pi. The cloud workflow does not replace Pi files.

Read complete v0.9.0 notes

v0.8.0

Roster polish and remote kiosk pairing

The roster is now the page focus, organization theming is more consistent, and a fresh Pi can be paired from a phone or laptop without typing Cloudflare details on its touchscreen.

Before upgradingDownload an Entire installation backup, then manually run Install or upgrade LancerLogin in the private deployment repository with Upgrade and Latest stable.

Read complete v0.8.0 notes

v0.7.0

Verified integrations

Google, Resend, and Discord now show Configured only after a real end-to-end proof; setup cards are quieter and guide each copy-and-paste action in place.

Before upgradingDownload an Entire installation backup, then manually run Install or upgrade LancerLogin in the private deployment repository with Upgrade and Latest stable.

Read complete v0.7.0 notes

v0.6.1

Kiosk status badge spacing

Physical-kiosk and browser-simulator names now retain a clear gap from roomier status badges, including when the card wraps at narrow widths.

Before upgradingDownload an Entire installation backup, then manually run Install or upgrade LancerLogin in the private deployment repository with Upgrade and latest.

Read complete v0.6.1 notes

v0.6.0

Recurring meetings and dashboard refinement

Create bounded daily, weekly, biweekly, or monthly meeting series, then search and edit every meeting attribute from one complete table.

Before upgradingDownload an Entire installation backup. Then manually run Install or upgrade LancerLogin in the private deployment repository, choose Upgrade, keep latest selected, and verify the exact installation slug. The dashboard cannot start the deployment itself.

Read complete v0.6.0 notes

v0.5.0

Attendance lifecycle and operations home

Meetings now require an end time. Members scan on arrival and departure; one scan is active, a pair is present, and incomplete attendance becomes absent after one organization-wide late-scan allowance.

Before upgradingDownload an Entire installation backup. Then manually run Install or upgrade LancerLogin in the private deployment repository, choose Upgrade, keep latest selected, and verify the exact installation slug. Discord contest buttons require rotating the optional Discord configuration with its application public key and displayed Interactions Endpoint URL.

Read complete v0.5.0 notes