v4.0.1

4.0.1 — the application tells you about updates. The MCP engine behaves exactly as in 4.0.0; this release is the interface, the packaging and the metadata.

What changed

• Updates are visible in the window. Options → Updates shows the version you run and its channel, the version on offer, Check now, the download progress, Restart to update, the time of the last check and the release notes. A mark on the sidebar says an update exists, and a notification is posted once per version. Downloading is a click and installing is a second one, or happens when you quit: nothing restarts under a command waiting for your approval without telling you. The npm engine and a browser tab (ssh-manager control) see none of it.
• Servers: the grid/list switch sits beside the search field instead of wrapping onto a line of its own below the group filters.
• The interface is built when the package is made, not committed. The package and the desktop application carry the built interface as before. That change alone produced exactly the bytes of 4.0.0's interface in the npm package and in the application (checked before this release's interface changes).
• Easier to find: the npm description and keywords, the MCP registry description and the GitHub About box say what V4 is. The README opens with what the project is and ends with the questions people ask; a code of conduct, issue forms and a pull request template are added.
• The primary button's hover state no longer drops white-on-orange text below the 4.5:1 contrast AA asks for.

Unchanged, and checked

The release pipeline upgrades the registry's 3.8.5, 3.8.6, 3.8.7 and 4.0.0 to this version and back, comparing the effective configuration fields, all 37 tool schemas and the server listings, and checking that no interface, listener, prompt or vault starts by itself.

Getting it

npm	npm update -g mcp-ssh-manager
Desktop app	Installed copies of 4.0.0 and of the 4.0.0 betas are offered it by their built-in updater; or ssh-manager app, or the files below.
Homebrew	brew upgrade ssh-manager

Platform	File	Signature
macOS, Apple silicon / Intel	SSH-Manager-4.0.1-arm64.dmg / -x64.dmg	Signed and notarized by Apple
Windows x64 / arm64	SSH-Manager-4.0.1-setup.exe	Not code-signed — see below
Linux x64	.deb, .AppImage	Unsigned, as Linux packages usually are

Windows: not code-signed in this release either

Like 4.0.0, the Windows installer and application are not Authenticode-signed: the public code-signing certificate still waits on the company's registration. Windows shows "Windows protected your PC": choose More info → Run anyway. Check the installer against the SHA-256 in release-manifest-win32.json on this release; ssh-manager app does it for you and installs only a file that matches.

Verifying

The npm package is published from CI with provenance and an attested SBOM (sbom.cyclonedx.json below). Each desktop platform has a release-manifest-*.json with every file's size and SHA-256. The full list of changes is in the CHANGELOG.