Configure no timetable mirrors while GTT blocks CI runners
Summary
src/transit-data/config.ts
-TIMETABLE_MIRRORS = [GitHub Pages, rolling `gtt-timetable` prerelease]
+TIMETABLE_MIRRORS = [] // GTT refuses connections from GitHub-hosted runners
src/services/notices.ts
-"…versioni più recenti … vengono scaricate da avoid-quest.github.io, github.com, …"
+"…gli aggiornamenti arrivano con le nuove versioni dell'app; … l'app legge da gtt.to.it solo l'elenco corse e i calendari…"
The optional timetable freshness layer cannot run in GitHub Actions: www.gtt.to.it refuses TCP connections from GitHub-hosted runners. With no mirror configured, phones make no mirror requests (no IP exposure for nothing). Live boards are unaffected: the bundled package, the direct GTT identity remap and GTT realtime do not depend on mirrors. "Aggiorna orari" still retries the remap. The pipeline and workflow stay in the repo (workflow disabled) for a future host that can reach GTT.
Evidence
- Before: workflow run 41364495321 failed twice in "Download (conditional), compact, validate" with
URLError: <urlopen error timed out>; the same URL answered200in 59 ms from an Italian connection. - After:
bun run verify→ typecheck, lint, 434 tests;updateSupportedis false with an empty list and no manifest request is made.
Merge Danger
Door: two-way
Re-adding the mirror entries restores the previous behaviour.
Blast Radius: transit-data
Only the optional manifest/package refresh; boards and remap unchanged.
Summary by cubic
Disables the timetable mirror configuration because GTT's static-export host refuses connections from GitHub-hosted runners, and updates the in-app privacy notice accordingly.
- With no mirrors configured, devices make no mirror requests; timetable freshness now comes with app releases.
- The direct GTT identity remap and realtime feed are unaffected, so live boards keep working.
- The documentation now records why mirrors are off and what re-enabling requires.