Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 7, 2025

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
acorn-io/acorn minor v0.6.0 -> v0.14.0

Release Notes

acorn-io/acorn (acorn-io/acorn)

v0.14.0

Compare Source

We’re excited to announce the release of Obot MCP Gateway v0.14.0. This update introduces support for the MCP Registry API.

MCP Registry API
Obot users can now connect to /v0.1/servers on Obot to access the MCP Registry API. This is compatible with any MCP client that supports custom MCP server registries.

For more details, see the documentation.

Getting Started

Try the live demo: chat.obot.ai

Install on Docker:

docker run -d --name obot -p 8080:8080 -v /var/run/docker.sock:/var/run/docker.sock \
ghcr.io/obot-platform/obot:latest

For more, see our Documentation

Full changelog

More details: obot-platform/obot@v0.13.0...v0.14.0

Thanks to Our Contributors

Thank you to everyone who contributed to this release or tried out Obot!

v0.13.0

Compare Source

We’re excited to announce the release of Obot MCP Gateway v0.13.0. This update introduces composite MCP servers, fine-grained tool access control, expanded audit capabilities, new admin tools, and a range of improvements across the UI, backend, and deployment experience.

Big Updates

Composite MCP Servers and Fine-Grained Tool Access Control
Admins and owners can now create and manage composite MCP servers, allowing them to combine multiple servers into a single deployment and enable or disable specific tools for each server. This provides both the ability to build complex, multi-server environments and to exercise fine-grained control over tool access for users.

Audit Log Export
Admins and auditors can now export audit logs directly from the UI, making it easier to review and archive system activity.

Server Scheduling and Resource Controls
Admins and owners can now centrally configure global resource requests, limits, scheduling policies, and pod annotations for all MCP servers running on Kubernetes. This can be managed through the UI or the Helm chart, giving you greater control and consistency across your Kubernetes deployments.

Update Notification for Admins and Owners
Admins and owners will now receive notifications in the UI when a new version of Obot is available. This update check can be turned off by setting the environment variable OBOT_SERVER_UPDATE_CHECK_INTERVAL_MINS to 0.

Improved Auth Provider Setup
We’ve simplified the first-time setup process, making it easier and more intuitive to configure and manage authentication and model providers from the start.

Other Notable Improvements

  • Improved handling and display of webhook statuses and error notifications.
  • More robust session management and user role handling.
  • Documentation updates, including new guides for deploying on AWS, Azure, and GCP, and expanded Kubernetes deployment instructions.
  • Security and dependency updates, including CVE fixes and a new SECURITY.md.
  • Numerous bug fixes for table scaling, sorting, project sharing, and more.

Upgrade Notes and Known Issues

  • This release removes certain legacy gptscript tools that were previously deprecated. Most users should be unaffected, but if you've been using Obot since before we converted from GPTScript to MCP and notice issues, please reach out.
  • After updating a composite MCP server, you must manually refresh the page to clear the "Update Required" banner.
  • Edit/update operations for running composite MCP servers may take up to a minute to complete.
  • Project sharing is not available for projects containing composite MCP servers.
  • Tool previews cannot be generated for composite MCP servers in this release.

Getting Started

Try the live demo: chat.obot.ai

Install on Docker:

docker run -d --name obot -p 8080:8080 -v /var/run/docker.sock:/var/run/docker.sock \
ghcr.io/obot-platform/obot:latest

For more, see our Documentation

Full changelog

Full Changelog: obot-platform/obot@v0.12.0...v0.13.0

Thanks to Our Contributors

Thank you to everyone who contributed to this release or tried out Obot!

v0.12.0

Compare Source

We’re excited to announce the release of Obot MCP Gateway v0.12.0! This release brings powerful new roles, expanded audit capabilities, and a wide range of UI, backend, and integration improvements.

✨ Big Updates

  • Auditor & Owner Roles: New roles separate system management from sensitive data access — only Auditors can view all server and chat details, while only Owners can assign the Auditor role. Admins can no longer see these sensitive details unless they’re also assigned as Auditors.
  • Admin Dashboard Upgrades: New "Deployments and Connections" dashboard for easily visualizing and operating on MCP servers in bulk.
  • Okta Group Support for Access Control Rules: You can now use Okta groups when configuring Access Control Rules, making it easier to manage permissions with your existing identity provider.
  • Customizable Remote MCP Connections: Authors can now configure Remote MCP entries with user-supplied or static HTTP headers, and inject user-supplied values into templated URLs.
  • Expanded Power User Capabilities: Power Users and Power User Plus now have access to usage stats and audit log metadata (excluding sensitive data) for their MCP servers.
  • Kubernetes & Helm Enhancements: Helm charts now support affinity, tolerations, nodeSelector, and Kubernetes-recommended labels for smoother deployment and upgrade of Obot.

🛠 Other Notable Improvements

  • UI/UX Polish: Refined navigation, dynamic chevrons, improved table columns, and enhanced project sharing styling.
  • Sensitive Data Handling: Better masked value display and multi-line support in sensitive fields.
  • Database & Logging: Improved DB logging and clarified requirements.
  • Bug Fixes: Numerous fixes for table filtering, sorting, admin tools, and Safari-specific UI issues.
  • Documentation: Expanded guides, including improved Entra setup walkthroughs.

⚠️ Important Upgrade Notes

Please review the following before upgrading:

Transition to Owner Role

The new Owner role now sits above the Admin role as the most privileged role in the system. To leverage it's ability to assign the Auditor role, you must assign one or more initial Owners via the OBOT_SERVER_AUTH_OWNER_EMAILS environment variable. This has the same semantics as the OBOT_SERVER_AUTH_ADMIN_EMAILS environment variable.

Embedded DB no longer the default for Helm installs

For Helm installs, Obot no longer defaults to a built-in Postgres database. An external database is required for production setups, but the embedded database remains available for evaluation. You must either provide a database connection string via config.OBOT_SERVER_DSN, or explicitly opt into the embedded database for testing by setting dev.useEmbeddedDb to true.

If you are upgrading and were previously using the embedded database, you must set the dev.useEmbeddedDb to true when you upgrade.

Okta users have to update their issuer URL

For Okta users, after updating to this release, you will need to modify the Issuer URL in the Okta auth provider configuration. This is due to our new support for Okta groups.

You must set it to https://.okta.com with no path in the URL.
See https://docs.obot.ai/configuration/auth-providers#okta-enterprise-only for more information, as there are some settings you must tweak in your Okta workspace in order for Obot to work with the groups in your directory.

If you find that you are unable to log in to adjust this setting, restart Obot with the environment variable OBOT_SERVER_FORCE_ENABLE_BOOTSTRAP=true so that you can log in as the bootstrap user again in order to change the setting.

📜 Full changelog

Full Changelog: obot-platform/obot@v0.11.0...v0.12.0

🚀 Getting Started

  • Try the live demo: chat.obot.ai
  • Install on Docker:
    docker run -d --name obot -p 8080:8080 -v /var/run/docker.sock:/var/run/docker.sock \
    ghcr.io/obot-platform/obot:latest
  • For more, see our Documentation

🙌 Thanks to Our Contributors

Finally, a special welcome and thank you to @​nlamirault for their first contribution to this release!

v0.11.0

Compare Source

We’re excited to announce the fourth public beta release of the Obot MCP Gateway (v0.11.0)!
This release brings major new features for power users, project sharing, and security, along with a host of UI/UX improvements and backend enhancements.

✨ Big Updates

  • Project Templates & Shareable Links: Easily create, share, and reuse project templates. Shareable links make collaboration and onboarding a breeze.
  • Power User Roles: Introducing “Power User” and “Power User Plus” roles for advanced access and management capabilities.
  • MCP Publisher App: Power users can now publish and manage MCP resources with a dedicated publisher app.
  • JWT-based OAuth Tokens: MCP now uses JWT for OAuth tokens, improving security and interoperability.
  • Audit Log Encryption: Sensitive parts of MCP audit logs are now encrypted for enhanced security.

🛠 Other Notable Improvements

  • Project Sharing: Improved UI and reliability for sharing projects, including retention of task runs and better change detection.
  • Table Enhancements: Table cells are now resizable, with new header column filters for easier data exploration.
  • Enterprise UI Tag: Enterprise edition is now surfaced in the UI, with enterprise info available via the version API.
  • Editor & Input Improvements: New Milkdown plaintext editor for chat input, better handling of multi-value fields, and improved copy-paste support.
  • MCP Docker Backend: Backend improvements for more robust Docker support and global MCP URLs.
  • Access Control: More accurate detection and enforcement of access rules, especially for new user roles.
  • UI/UX Polish: Numerous fixes and enhancements, including better tool info, improved scrollbars, and more responsive dialogs.
  • Documentation: Expanded docs on architecture, filters, and authentication providers.

📜 Full changelog


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Feb 7, 2025
@renovate renovate bot force-pushed the renovate/acorn-io-acorn-0.x branch from 04d17d0 to 3bdd167 Compare March 17, 2025 18:03
@renovate renovate bot changed the title chore(deps): update dependency acorn-io/acorn to v0.6.1 chore(deps): update dependency acorn-io/acorn to v0.7.0 Mar 17, 2025
@renovate renovate bot force-pushed the renovate/acorn-io-acorn-0.x branch from 3bdd167 to b550604 Compare March 25, 2025 19:29
@renovate renovate bot changed the title chore(deps): update dependency acorn-io/acorn to v0.7.0 chore(deps): update dependency acorn-io/acorn to v0.7.1 Mar 25, 2025
@renovate renovate bot force-pushed the renovate/acorn-io-acorn-0.x branch from b550604 to 77d9d47 Compare August 9, 2025 00:52
@renovate renovate bot changed the title chore(deps): update dependency acorn-io/acorn to v0.7.1 chore(deps): update dependency acorn-io/acorn to v0.8.0 Aug 9, 2025
@renovate renovate bot force-pushed the renovate/acorn-io-acorn-0.x branch from 77d9d47 to 5ed8257 Compare August 29, 2025 01:08
@renovate renovate bot changed the title chore(deps): update dependency acorn-io/acorn to v0.8.0 chore(deps): update dependency acorn-io/acorn to v0.9.0 Aug 29, 2025
@renovate renovate bot force-pushed the renovate/acorn-io-acorn-0.x branch from 5ed8257 to 9c4967b Compare September 3, 2025 20:22
@renovate renovate bot changed the title chore(deps): update dependency acorn-io/acorn to v0.9.0 chore(deps): update dependency acorn-io/acorn to v0.10.0 Sep 3, 2025
@renovate renovate bot force-pushed the renovate/acorn-io-acorn-0.x branch from 9c4967b to ba418c9 Compare September 23, 2025 05:40
@renovate renovate bot changed the title chore(deps): update dependency acorn-io/acorn to v0.10.0 chore(deps): update dependency acorn-io/acorn to v0.11.0 Sep 23, 2025
@renovate renovate bot force-pushed the renovate/acorn-io-acorn-0.x branch from ba418c9 to 36d8f91 Compare October 17, 2025 00:47
@renovate renovate bot changed the title chore(deps): update dependency acorn-io/acorn to v0.11.0 chore(deps): update dependency acorn-io/acorn to v0.12.0 Oct 17, 2025
@renovate renovate bot force-pushed the renovate/acorn-io-acorn-0.x branch from 36d8f91 to 955006e Compare November 8, 2025 00:50
@renovate renovate bot changed the title chore(deps): update dependency acorn-io/acorn to v0.12.0 chore(deps): update dependency acorn-io/acorn to v0.13.0 Nov 8, 2025
@renovate renovate bot force-pushed the renovate/acorn-io-acorn-0.x branch from 955006e to 8450148 Compare December 4, 2025 02:27
@renovate renovate bot changed the title chore(deps): update dependency acorn-io/acorn to v0.13.0 chore(deps): update dependency acorn-io/acorn to v0.14.0 Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant