Songr 1.4.7

Songr 1.4.7

This release protects the Roon pairing token on Windows and fixes the desktop
app's settings window for some install folders.

• Windows: the Roon pairing token is now private. Songr keeps the token it
  uses to pair with your Roon Core in a file. On Windows that file could be
  read by every account on the computer, because it inherited its folder's
  permissions (under C:\Program Files, every user can read). Songr now gives
  the token file only the account that runs Songr, SYSTEM and Administrators.
  It does the same to the token's folder when that folder is Songr's own
  configuration folder (CONFIG_DIR) or one Songr created for it. If you set
  ROON_TOKEN_PATH to a file in some other existing folder, Songr leaves that
  folder's permissions alone and protects only the token file.
• Upgrading on Windows: an existing token is protected the first time the
  upgraded Songr connects to your Roon Core. You do not need to pair again.
  Other systems are unchanged; the token file was already private there.
• Desktop app: the settings window now opens and saves when the app is
  installed in a folder whose path contains ~, [ or ]. Before, it refused
  to load or save its own settings there.

Desktop app: as in 1.4.6, the app runs Songr on the Node.js built into
Electron, which is Node.js 24.22.0 and predates the October 2026 Node.js
security fix. By default the app only accepts connections from the computer it
runs on. If you have turned on Serve on the local network ("Allow other
devices on my network"), other devices on your network can reach it;
compressed request bodies are refused there too. A later desktop release will
move to an Electron built on Node.js 24.22.1 or newer once a stable one exists.

The Windows installer for this release is not code-signed. Windows may warn
that it comes from an unknown publisher; choose More info, then Run
anyway, to install.

Application identity, pairing and saved settings are retained when upgrading.