See the CHANGELOG for details.
MusicBee Microsoft Store version
If you are using the Microsoft Store version of MusicBee, install the plugin using the zip file.
Go to MusicBee -> Edit -> Preferences -> Plugins and use the "Add Plugin" button to install directly from the zip file.
Verify integrity
To verify the downloaded file integrity you can use Windows PowerShell:
cd Downloads
Get-FileHash -Path .\musicbee_remote_1.5.0-beta.3.exe -Algorithm SHA512Ensure that the Hash matches the one in the corresponding .sha512 file.
Verify authenticity
A hash only proves the download was not corrupted. To prove the files came
from this project, verify a signature.
manifest.json lists the SHA512 of every published artifact and is signed
with the project's release key. This is what the plugin's own updater checks
automatically; the key is built into the plugin, so it needs nothing extra.
To check it yourself, easiest first:
With the GitHub CLI (already installed for many, winget install GitHub.cli):
gh attestation verify musicbee_remote_1.5.0-beta.3.zip --repo musicbeeremote/mbrc-plugin
With minisign, which also works
fully offline (winget install jedisct1.minisign):
minisign -Vm manifest.json -P RWSvA74oRp/zMFdIdbo3fPVjT4DPO7jaZPOwKY/ca0Oa9j+SeKbMbRq5
then check that the sha512 values in manifest.json match the files you
downloaded. All release public keys are committed at
packages/mbrc-release/keys/.
What's Changed
- fix(ci): stamp the release version the updater actually reads by @kelsos in #176
- fix(update): remove the staging directory a successful update leaves behind by @kelsos in #177
- fix(plugin): open the log folder on the Store build by @kelsos in #178
- fix(update): make the Store build's update path diagnosable, and try to fix it by @kelsos in #179
- chore: add git hooks and enforce conventional commits by @kelsos in #180
- fix(hooks): mark commit-msg executable by @kelsos in #181
- fix(plugin): read now-playing list tags by index, not by url by @kelsos in #182
Full Changelog: v1.5.0-beta.2...v1.5.0-beta.3