Release v4.9: lock a profile to fixed peer addresses (#17)
Ships the per-profile "Lock to these exact peer addresses, no matter what" toggle. Version 4.9; About changelog + RELEASE_NOTES added. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
c7d422e3ba
commit
d7f6d9fd9d
@@ -20,6 +20,27 @@ internal sealed class AboutDialog : Form
|
||||
/// updates" path.</summary>
|
||||
private const string ReleaseNotes =
|
||||
"""
|
||||
RemSound v4.9
|
||||
|
||||
Lock a profile to fixed addresses.
|
||||
|
||||
RemSound normally finds the other computer by the
|
||||
name it advertises on the network, and follows it
|
||||
if it turns up at a new address. Handy — but not
|
||||
what you want if a machine has two addresses (say
|
||||
a VPN one and a local one) and you only ever want
|
||||
the one you chose.
|
||||
|
||||
A new tickbox on the Connectivity tab — "Lock to
|
||||
these exact peer addresses, no matter what" — pins
|
||||
a profile to exactly the addresses you set. With
|
||||
it on, RemSound never matches by name and never
|
||||
switches address; if the address you set stops
|
||||
working, the connection simply waits rather than
|
||||
wandering to another. Off by default, and saved
|
||||
per profile, so you can lock one profile down
|
||||
while another keeps the automatic behaviour.
|
||||
|
||||
RemSound v4.8
|
||||
|
||||
A rare crash fixed, and crash reports for next
|
||||
|
||||
@@ -14,7 +14,7 @@
|
||||
tag_name on the latest GitHub release; bump it on every public release. The
|
||||
AssemblyVersion / FileVersion default to this value, and Assembly.GetName().Version
|
||||
is what the About dialog and the updater both read. -->
|
||||
<Version>4.8</Version>
|
||||
<Version>4.9</Version>
|
||||
</PropertyGroup>
|
||||
|
||||
<ItemGroup>
|
||||
|
||||
Reference in New Issue
Block a user