v0.2.0

Alpha. Breaking changes can happen in any release: an event file from an older version may not open in a newer one. Finish an event on the version you started it with, and keep a paper backup.

Changes since v0.1.0

• Timing: a gate keeps each detection until the server has stored it, so a database outage loses no time
• Timing: a finish or split that arrives before its delayed start still counts once the start is in
• Hardware: gates waiting for approval sit in the gate list, Pair gates counts down while open, and the list keeps only status, last read and clock
• Standalone: a port clash names the program holding the port, and Windows and the Pi installers reserve the rally ports
• Gates: a second of silence between two status sounds, so each one stays recognisable
• ESP32 Gate: settings need Open gate config on the Hardware page like a Pi gate, and the browser installer keeps the gate's key and settings
• Gate Config: changes on the rally Wi-Fi need Open gate config on the Hardware page; the gate's own hotspot and its first 3 minutes after switching on stay open
• ESP32 Gate: logs in with its own key and waits on Hardware until the organiser pairs it, like a Pi gate
• Gates: each gate logs in with its own key, new gates wait on Hardware until the organiser pairs them
• Access: visitors without a login see a public page with start lists, live times and results; everything else needs a login
• Access: the organiser password locks for a minute after five wrong tries, and the login page says participants stay off the timing Wi-Fi
• Entries: a History on each entry names every hand-made change to its results, with the device and the value before and after
• Access: invitations with printable QR codes on Setup, log in by scanning, and every page shows only what the role may change
• Access: every change needs a login with a role, from an invitation code, the organiser password or the server machine itself
• Dashboard: no other web page can reach the API anymore, the dev server proxies it instead
• Gates: a mistyped setting stops the gate and its settings page marks the field, instead of timing with a broken value
• Gates: one rule for gate names everywhere, A–Z, 0–9 and _, at most 32, typed letters become capitals
• Gates: the buzzer says when a gate has power, is ready, lost the server, has no synced clock or raised its hotspot
• Gates: a combined gate beeps on the beam and forwards only paired passings, beam-only on request
• ESP32 gates: built on PlatformIO's espressif32 7.1.3
• Dependencies: NestJS 12
• Headless server: Postgres 18, restore the pre-update backup after installing
• Dependencies: TypeScript 6.0 in every workspace
• Database: TypeORM 1.1
• MQTT broker: Aedes 1.2
• Dependencies: better-sqlite3 12
• Dependencies: ESLint 10
• Dependencies: ulid 3, class-validator 0.15, Jest 30 for gate-config, Python 3.14 in CI
• Dependencies: latest minor and patch releases
• Node.js 24 everywhere: gate installer upgrades an older Node
• Standalone packages: Windows starts from Rally Gate.exe with the logo, everything else tidied into app/
• ESP32 gates: the no-port dialog in the dark theme too
• ESP32 gates: image named like the packages, without the v

v0.1.0

Alpha. Breaking changes can happen in any release: an event file from an older version may not open in a newer one. Finish an event on the version you started it with, and keep a paper backup.

First release. What it does: What works today.