chore(deps): update dependency acorn-io/acorn to v0.14.0 #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.6.0->v0.14.0Release Notes
acorn-io/acorn (acorn-io/acorn)
v0.14.0Compare 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/serverson 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:
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.0Compare 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
Upgrade Notes and Known Issues
Getting Started
Try the live demo: chat.obot.ai
Install on Docker:
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.0Compare 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
🛠 Other Notable Improvements
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_EMAILSenvironment variable. This has the same semantics as theOBOT_SERVER_AUTH_ADMIN_EMAILSenvironment 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 settingdev.useEmbeddedDbtotrue.If you are upgrading and were previously using the embedded database, you must set the
dev.useEmbeddedDbto 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=trueso 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
🙌 Thanks to Our Contributors
Finally, a special welcome and thank you to @nlamirault for their first contribution to this release!
v0.11.0Compare 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
🛠 Other Notable Improvements
📜 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.
This PR was generated by Mend Renovate. View the repository job log.