github obot-platform/obot v0.26.1

3 hours ago

This is a patch release for v0.26.0. It fixes bugs in vMCP profiles and the vMCP UI, makes group lookups against the auth provider more resilient, and adds support for Bitbucket Cloud catalogs.

Important

This is not the upgrade patch release. The v0.26.0 notes said that existing installations should not upgrade to v0.26.0, and that upgrade support for vMCPs would follow in a patch release. v0.26.1 does not include that upgrade support. The patch release with upgrade support is planned for next week. Until then, the guidance from v0.26.0 still applies: existing installations should not upgrade to v0.26.1, and only net new installations should install it. See #7802 for details.

Fixes and Improvements

  • vMCP profiles are more predictable. A profile created by enabling every tool now saves that list of tools instead of being treated as an "As-is" profile. Profiles can refresh their tool list after the underlying MCP server changes, and users are told when a tool change on a component affects existing profiles. Tools that a profile lists but the server does not allow are now removed from the profile instead of causing an error.
  • When an MCP server used by a vMCP is modified, the vMCP now shows that an update is available and offers the update action. The vMCPs page can also be filtered by connection state.
  • vMCP profiles now tell apart groups that come from the identity provider and groups that Obot manages, so administrators can see where a group grant comes from when assigning groups to a profile.
  • Group lookups against the auth provider no longer fail logins when the provider rate limits Obot. Concurrent lookups for the same user are combined into one call, and after a failed lookup Obot uses the groups it already has until a short cooldown passes.
  • Fixed a bug where vMCPs and npx/uvx servers rejected valid MCP list requests that omitted the optional params field.
  • Connections to Kubernetes-hosted MCP servers now retry briefly while a server's pod is being replaced, instead of failing right away.
  • MCP and Skills catalogs can now use Bitbucket Cloud repository URLs, with or without .git. Private repositories can authenticate with a personal API token or a repository access token.
  • The maximum repository size for Git-backed catalogs can now be set with --git-max-repo-size-mb or OBOT_SERVER_GIT_MAX_REPO_SIZE_MB. The default is still 100 MB.
  • Smaller UI fixes: the message policy navigation links are restored, the local login page focuses the email field, and the auth provider page explains how to change or discard a staged provider switch.

What's Changed

New Contributors

Full Changelog: v0.26.0...v0.26.1

Don't miss a new obot release

NewReleases is sending notifications on new releases.