Skip to content

Version Packages - #322

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

Version Packages#322
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@sei-js/mcp-server@0.4.0

Minor Changes

  • e0e4720: Remove the search_sei_js_docs tool and route the remaining search_docs tool through the official docs.sei.io MCP endpoint instead of the legacy Mintlify/Trieve backends. Reconnect and retry once when the remote docs session expires so callers do not see a transient 404 or 410 error. Remove the obsolete docs/ rule from the package's .npmignore.

@sei-js/registry@1.0.5

Patch Changes

  • d12ad96: Stop running Git submodule commands when consumers install the registry package.

@cursor

cursor Bot commented Aug 10, 2026

Copy link
Copy Markdown

PR Summary

Medium Risk
The MCP server removes a public tool and depends on the remote docs.sei.io MCP for search_docs; registry install behavior changes but is limited to dropping submodule commands.

Overview
This is a Changesets release PR: it bumps versions, updates package changelogs, and removes the consumed changeset files so npm can publish @sei-js/mcp-server@0.4.0 and @sei-js/registry@1.0.5.

@sei-js/mcp-server (minor) drops the search_sei_js_docs tool and sends search_docs through the official docs.sei.io MCP endpoint instead of legacy Mintlify/Trieve backends. It reconnects and retries once when the remote docs session expires (avoiding transient 404/410), and drops an obsolete docs/ rule from .npmignore.

@sei-js/registry (patch) stops running Git submodule commands during install, so consumers are not pulled into submodule setup on npm install.

Reviewed by Cursor Bugbot for commit 88979d8. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 9e0d255 to 88979d8 Compare August 10, 2026 23:28
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.

0 participants