Files
meshcore-analyzer/docs/release-notes/v3.18.0.md
T
efiten 12f9c5c686 docs(release): v3.18.0 release notes and changelog entry (#2420)
Release notes and changelog entry for v3.18.0, to be tagged on this PR's
merge commit.

- `docs/release-notes/v3.18.0.md`: the notes, in the same shape as
v3.17.0. The CI/CD Pipeline uses this file as the GitHub release body.
- `CHANGELOG.md`: a 3.18.0 entry under `[Unreleased]`.

11 commits since v3.17.0: 5 fix, 3 feat, 1 test, 1 refactor, 1 docs.
"Read this before upgrading" covers the `users.db` schema v9 migration
with user accounts on (#2415), the WebSocket path `/ws` (#2383) and
config tile URLs winning on the Map and Live pages (#2386).

Documentation only, no code change.
2026-11-17 16:42:05 +01:00

5.4 KiB

v3.18.0

11 commits since v3.17.0: 5 fix, 3 feat, 1 test, 1 refactor, 1 docs. Three feats, so minor not patch.

A short release with three larger features. Two are optional tools: radio line of sight on packet routes plus a repeater planner, and repeater details that registered users can fill in. The third is a new way to deploy the UI: from its own web container or from a static host such as Cloudflare Pages. An instance that keeps running the one container it runs today needs no configuration change.

Read this before upgrading

With user accounts on, users.db moves to schema v9

With userManagement.enabled, the first start creates the tables for repeater claims and details (#2415). A v3.17.x binary refuses the database afterwards ("database schema version 9 is newer than this binary supports"), so keep a copy of users.db from before the upgrade if you may want to roll back. The analyzer database is not touched. Without user accounts nothing changes.

The live feed connects to /ws

The UI's WebSocket now goes to /ws instead of / (#2383). The server has answered on /ws for a long time and still accepts /, so open browsers keep working. A reverse proxy that forwards WebSocket upgrades only for an exact / must forward /ws too. The nginx example in docs/deployment.md (location /) already covers it.

Map tile URLs you set in the config now win on every page

If your config sets a tile URL (tiles.dark, tiles.light, map.tiles.darkUrl or map.tiles.lightUrl), the Map and Live pages now use it too (#2386). Before, a visitor's tile pick in the customizer overrode it on those two pages, while the node pages, reach map and analytics already followed your setting. Without those keys nothing changes.

Features

  • Radio line of sight on packet routes (#2391). With los.enabled, every leg of a packet route on the map gets a clear, marginal or blocked chip (first Fresnel zone, k=4/3), obstructions are marked on the map, and a terrain profile panel lets viewers change antenna height and frequency. Set los.frequencyMhz to your mesh's frequency: the default 910.525 is the US one, use 869.618 for EU/UK.
  • Repeater planner (#2391). With planner.enabled, #/tools/planner checks line of sight along a chain of points, finds the best single relay between two points, and suggests new repeater sites that join the existing backbone in an area of up to 100 by 100 km. Both features use SRTM terrain (about 90 m) fetched on demand from AWS Open Data and kept in memory only; the server still writes nothing. Both are off by default, and with them off nothing is fetched.
  • Repeater info and claims (#2415, #2416, #2417). With user accounts on, registered users can claim a repeater and record what the radio cannot advertise: antenna height and gain, power source, whether it is active, in maintenance or decommissioned, and notes. Everyone sees the details on the node page. A claimed repeater can be edited by its claimers and by admins only; edits and claims show in the audit log, and admins can remove a claim.
  • Three ways to deploy the UI (#2383). Next to the all-in-one container you run today, the UI can now come from a separate web container (Caddy, Dockerfile.web and docker-compose.split.yml) that forwards the API, or from a static host or CDN against your server on another origin. The static build has no logins; its account pages link to the classic UI. docs/deployment.md has a "Deployment modes" section, and deploy/static/README.md covers Cloudflare Pages and rollback.

Fixes

  • Memory after eviction (#2327). Packets removed from memory were still held by some secondary indexes, so memory use stayed higher than the data in it. In a synthetic test with the same live data the retained heap went from 98 to 27 MiB.
  • Scope statistics (#2368, closes #2364). /api/scope-stats counted flood and direct traffic as unscoped but left them out of transportTotal, so an unscoped share could pass 100%. The summary now has a total and splits unscoped into transport, flood and direct; existing fields keep their values. The Scopes tab shows the split.
  • Light-mode maps on node pages (#2386). The node page map ignored the light tile provider picked in the customizer, could show Carto's "API key required" watermark when the config arrived late, and did not follow a theme switch. It now uses the same tile choice as the main map and follows changes while open.

Tests, refactoring and docs

The tile-resolver unit test loads CSApi before roles.js (#2402), and the Live page reuses the shared timestamp renderer (#2395). Superseded repeater liveness plans were moved to the archive (#2392).

Issues closed

  • #2364 /api/scope-stats: unscoped can exceed transportTotal since #1838

Contributors

Pull requests: efiten (3, maintainer), n30nex (3), zfouts (2), ppicazo, SaarMesh-Bot and trixmoe (1 each). efiten co-authored #2391.

Issues: Nursedude for the scope statistics report in #2364.

Upgrade notes

  • Created automatically: the repeater claim and detail tables in users.db (schema v9), only with user accounts on.
  • Opt-in: los.enabled, planner.enabled (with the shared terrain block), the web container and the static build.
  • Action needed: a reverse proxy that forwards WebSocket upgrades only on / must also forward /ws. Keep a pre-upgrade copy of users.db if you run user accounts.