Skip to content

fix(mcp): pin console install spec to @robosystems/mcp@latest#171

Merged
jfrench9 merged 1 commit into
mainfrom
feature/mcp-latest-spec
Jun 21, 2026
Merged

fix(mcp): pin console install spec to @robosystems/mcp@latest#171
jfrench9 merged 1 commit into
mainfrom
feature/mcp-latest-spec

Conversation

@jfrench9

Copy link
Copy Markdown
Member

Summary

The console config generator now emits <packageName>@latest so a stale globally-installed client can't shadow registry updates.

Why

Bare npx -y @robosystems/mcp runs an already-installed copy without checking the registry; @latest forces npx to resolve the current published version.

Changes

  • src/lib/core/components/console/ConsoleContent.tsx — config generator appends @latest

Testing

npm run lint clean; console component tests pass (23).

Note

ConsoleContent.tsx is the shared lib/core subtree (edited directly here for consistency). Run npm run core:push post-merge to align the canonical core. Part of a cross-repo sweep.

The console config generator (shared core subtree) now emits `<packageName>@latest` so a stale globally-installed client can't shadow registry updates.
@jfrench9 jfrench9 merged commit a7ff967 into main Jun 21, 2026
3 checks passed
@jfrench9 jfrench9 deleted the feature/mcp-latest-spec branch June 21, 2026 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant