EdnunpandClaude Opus 4.7
6b1ae2d017
The client and the relay server are published from the same GitHub repo; the server's releases use "server-" prefixed tags. RemSoundUpdater hit /releases/latest, which is repo-wide — when a server release was newest, the updater fed "server-v2.3" to ParseTag (-> a bogus 0.0.3) and concluded "up to date", silently skipping real client updates. CheckForUpdateAsync now lists /releases and picks the highest-versioned release whose tag is a RemSound client tag (new IsClientReleaseTag: after an optional leading "v", first char must be a digit). Drafts and pre-releases are skipped. The server-side updater already filters to "server-" tags, so client + server coexist in one repo cleanly. Also rewrites build-release.ps1 with a data-safety check: it publishes to a fresh staging folder and aborts the release if any logs/, profiles/, recordings/ folder, .log file or remsound.config.json is present in the staged output or the finished zip — preventing a repeat of the v1.5/v1.6 zips that shipped with developer logs and profiles. No wire-format or audio-pipeline changes — v1.5/v1.6/v1.7 interoperate. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
1.9 KiB
RemSound v1.7
A self-updater fix. Wire format and audio pipeline are unchanged from v1.4 / v1.5 / v1.6 — all releases interoperate.
Bug fix
- Check for updates now reliably finds RemSound releases. RemSound and the RemSound relay server are published from the same GitHub repository; the relay's releases use
server-prefixed tags. The updater previously asked GitHub only for the single newest release of any kind — so whenever a relay release was the most recent, the updater misread its version and concluded RemSound was already up to date, silently skipping a real client update. The updater now scans the full release list and considers only RemSound client versions, ignoring server releases, drafts and pre-releases.
If your copy is stuck on an older version because of this, install v1.7 once by hand (below) — from v1.7 onward, Help → Check for updates works correctly on its own.
Install
- Download
RemSound-v1.7.zipfrom this release. - Extract somewhere with write permission (e.g.
C:\RemSound\,Documents\RemSound\). AvoidProgram Filesunless you grant write permission so the self-updater can replace files in place. - Run
RemSound.exe. Allow on private networks when Windows Firewall prompts. - Press F1 (or use the Help menu) for the user manual.
Requires the .NET 10 Desktop Runtime. If it's missing, Windows offers to fetch it on first launch.
Upgrading
v1.5 / v1.6 users: use Help → Check for updates — it pulls v1.7 cleanly (their updater can still see v1.7 as long as it's the newest release at check time). To be certain, the manual install above always works.
If you installed RemSound inside a Dropbox-synced (or other file-sync) folder and your install is v1.0 / v1.1 / v1.2, see the v1.3 release notes for one-time manual install steps. From v1.3 onward Check-for-updates handles Dropbox correctly.