Repository navigation
File Bridge 1.18.1 — the panel stops reporting a version it is not
A one-line fix with a lesson attached, and a note on tag numbering.
The panel stopped reporting a version it is not
__VER__ is substituted when the HTML is served, and poll() never touched it.
The panel window is deliberately built to outlive a server restart — that is
what reviving on poll is for — so a panel left open across a Quit and relaunch
went on claiming whichever version served its page. Observed reading 1.17.0
against a 1.18.0 server.
That matters more here than it looks. The whole convention in this repo is three
independently versioned pieces, bump only what changed — and the panel is where
you read one of them. /api/status already returned version; the footer takes
it from there now.
Verified the way it actually breaks: serve the page from a 9.9.9 build, swap
the server underneath the still-open window, watch the footer correct itself with
no reload.
Filed as a dead end because it generalises: anything baked into that template
becomes a lie the moment the process is replaced. __LINK__ only gets away
with it because poll() overwrites it every 2.5 s.
Tag numbering realigns here
The repo tag and the component versions had drifted apart:
| Tag | shipped server |
|---|---|
| v1.17.0 | 1.18.0 |
| v1.16.0 | 1.15.0 |
| v1.15.0 | 1.14.0 |
| v1.14.0 | 1.13.0 |
Tagging this v1.18.1 makes the repo tag equal the server version again. The
tag has never tracked any one component and still does not promise to, but the
gap was a reliable way to misread which release contained what.
Carried from v1.17.0, worth repeating
That release contains the fix for the access key being written into
~/.filebridge/gui.log — the live key sat there 762 times at mode 644 while
~/.filebridge/key held the same secret at mode 600. A gui.log written
before v1.17.0 has your key in it in the clear. It is re-chmodded to 600 on
the next launch, but delete it if it was ever shared:
rm ~/.filebridge/gui.log
Two copies remain in a fresh log by design, from the startup banner printing the
full link — that banner is how you recover the link when the panel will not
open, so redacting it would remove the log's only real job. Two copies behind
mode 600 is the same protection the key file itself gets.
Versions
| Piece | Version |
|---|---|
| Server | 1.18.1 |
| Mac app | 1.18.1 |
| Android app | 1.13.0 (versionCode 16) — unchanged |
Debug-signed. Installs and upgrades in place, not Play Store distributable.