Skip to content

v1.1.27

Choose a tag to compare

View all tags
@db-lyon db-lyon released this 20 Jul 22:35
v1.1.27
ff3edab

v1.1.27

ue-mcp login authorizes a machine to publish plugins, so publishing needs no token handling at all.

Server

  • ue-mcp login runs the GitHub device flow and mints your own registry publish token, cached at ~/.ue-mcp/registry.json (owner-only permissions). Reuses the GitHub authorization already held for feedback authorship when present, so it usually completes without a browser round-trip. --force re-authorizes and rotates the token.
  • ue-mcp logout clears the cached token locally. The token stays valid until revoked at the registry's /account page.
  • plugin publish resolves its token as --token, then the environment, then the cached login. Existing CI setups using UE_MCP_PUBLISH_TOKEN are unchanged; a logged-in author no longer sets anything.
  • Re-running login rotates: previously minted CLI tokens are revoked, so a lost machine's token stops working. Tokens minted in the web UI are left alone.
Assets 3
Loading