wazionapps/nexo

Patch release — root-cause fix for the mcp_restart_required lockup that v7.11.2 only masked at the enforcer layer.

_FINGERPRINT_EXCLUDE_DIRS in src/runtime_versioning.py was missing "versions", so compute_mcp_runtime_fingerprint() walked into core/versions/<old>/**.py whenever it was called against the live runtime root. After the second-ever nexo update on a host, installed_runtime_fingerprint() (resolves through active_runtime_root() → core/versions/<active>/) and prime_process_fingerprint() (starts from __file__.parent → live core/) returned different hashes. The marker could never be cleared by _ack_current_client_if_restarted() and every non-allowlisted MCP tool returned {"error": "mcp_restart_required", "reason": "fingerprint_mismatch"} indefinitely — even after restarting the client.

v7.11.2 silenced the enforcer-side periodic reminders but the marker itself stayed stuck. Adding "versions" to _FINGERPRINT_EXCLUDE_DIRS restores parity: both fingerprint computations now hash the same set of files regardless of which entry path the caller starts from.

Recovery on hosts already locked: delete ~/.nexo/runtime/operations/{mcp-restart-required,fingerprint-cache}.json, restart any long-lived server.py processes, and the next tool call resolves cleanly.

See CHANGELOG.md and the blog post for the full write-up.

What's Changed

• Release 7.11.3: fingerprint excludes versions/ snapshot store by @wazionapps in https://github.com/wazionapps/nexo/pull/311

Full Changelog: https://github.com/wazionapps/nexo/compare/v7.11.2...v7.11.3