[Bug] MCP update feature suggests a downgrade

[danbarr]

Bug Description

If you run a newer version of an MCP server than what's in the registry, the desktop app suggests a downgrade to match the registry. Seems it's doing a simple match and not a semver-aware check?

In my case, I edited my playwright server to bump it to v0.0.77, but the UI is prompting me to downgrade to v0.0.70.

Steps to Reproduce

1. Run Playwright from the registry
2. Edit the workload to bump the image from the registry's v0.0.70 to v0.0.77
3. Note the update icon appears, suggesting a downgrade

Expected Behavior

The app should do a semver-aware check and only suggest an update if the registry version is newer than the running version.

Actual Behavior

No response

Priority

Low

Environment

App version: 0.36.6

Additional Context

No response

[samuv]

The problem here is that we don’t parse the semantic version we just check whether the version currently running differs from the one in the registry. 🤔

I’ll need to figure out whether I can move the upgrade logic to the new implementation in thv

[danbarr]

FWIW, that implementation isn't considering semver either, it just ends up thinking they aren't registry sourced at all:

NAME               STATUS                 CURRENT                                                  CANDIDATE                                      NEW-ENV   POSTURE
playwright         not-registry-sourced   mcr.microsoft.com/playwright/mcp:v0.0.77                 -                                              0         -
toolhive-doc-mcp   not-registry-sourced   ghcr.io/stackloklabs/toolhive-doc-mcp:v0.0.16-20260629   -                                              0         -