Skip to content

chore(mcp): upgrade docusaurus-plugin-mcp-server to 0.13.0, drop patch#125

Merged
jab3z merged 1 commit into
mainfrom
chore/upgrade-mcp-plugin-0.13
Jun 26, 2026
Merged

chore(mcp): upgrade docusaurus-plugin-mcp-server to 0.13.0, drop patch#125
jab3z merged 1 commit into
mainfrom
chore/upgrade-mcp-plugin-0.13

Conversation

@jab3z

@jab3z jab3z commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

What

Upgrades docusaurus-plugin-mcp-server 0.11.0 → 0.13.0 the safe way, and removes the fragile patch-package patch that blocked the two open Dependabot PRs (#123, #124).

Why the Dependabot PRs weren't mergeable

Both #123 and #124 bumped this package, and both would have broken the deploy:

  • A hand-written patch (docusaurus-plugin-mcp-server+0.11.0.patch, in both root and mcp-server/patches/) forced the FlexSearch index to a small footprint. The plugin's defaults — tokenize: "forward", resolution: 9, depth-2 bidirectional context — balloon the generated index to ~290MB and OOM the mcp service on deploy.
  • The patch is version-pinned to 0.11.0, so on 0.13.0 it silently fails to apply (patch-package only warns; npm ci still exits 0). The plugin would have run unpatched in production.
  • build(deps): bump docusaurus-plugin-mcp-server from 0.11.0 to 0.13.0 in /mcp-server in the npm-mcp-server group #123 additionally had a package.json ↔ lockfile desync (npm ci hard-failed, EUSAGE).

The fix

0.13.0 exposes the FlexSearch index config as a supported flexsearch plugin option — so no patch is needed. Config now lives in the two consumers (kept in sync):

  • docusaurus.config.ts — build-time index generation
  • mcp-server/server.mjs — runtime query-side index reconstruction

Both set flexsearch: { tokenize: "strict", resolution: 3, context: false }. The plugin's default encode() already lowercases + stems, so it's not overridden. Both patch files are deleted.

docusaurus-plugin-mcp-server is also ignored in dependabot.yml (both ecosystems) — it must be upgraded manually so the two configs stay in sync and the index size is re-verified.

Verification

  • npm run build → generated search-index.json is 2.8MB (cap is 50MB) ✅
  • Both npm ci install clean — lockfiles in sync ✅
  • npm run typecheck
  • mcp-server node test.mjs8 passed
  • End-to-end search smoke test against the built index returns relevant hits for payment, tokenization, webhook signature, refund ✅ (proves query-side config matches the index)

Follow-up

Supersedes the docusaurus-plugin-mcp-server part of #123 and #124. After this merges, #123 is closed and #124 is recreated (Dependabot, now ignoring this package) down to its 11 routine root bumps.

🤖 Generated with Claude Code

…op patch

0.13.0 exposes the FlexSearch index config as a supported plugin option
(`flexsearch`), so the hand-written patch-package patch that previously
forced the index small is no longer needed. The patch was version-pinned
to 0.11.0 and silently failed to apply on any bump (patch-package only
warns, npm ci still exits 0) — which would have shipped the plugin's
OOM-prone defaults (tokenize "forward", resolution 9, depth-2 context;
~290MB index) to production unnoticed.

Replaces the patch with explicit config in both consumers, which must
stay in sync:
- docusaurus.config.ts  — build-time index generation
- mcp-server/server.mjs — runtime query-side index reconstruction
Both set `flexsearch: { tokenize: "strict", resolution: 3, context: false }`.
The plugin's default encode() already lowercases + stems, so it is not
overridden.

Also ignores docusaurus-plugin-mcp-server in dependabot.yml — it must be
upgraded manually so the two configs are kept in sync and verified.

Verified:
- root `npm run build` -> search-index.json is 2.8MB (cap is 50MB)
- both `npm ci` install clean (lockfiles in sync)
- mcp-server `node test.mjs` -> 8 passed
- end-to-end search smoke test against the built index returns relevant
  hits for payment / tokenization / webhook signature / refund

Supersedes Dependabot PRs #123 and #124 (the docusaurus-plugin-mcp-server
portion); the 11 other root bumps in #124 are handled separately.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.

1 participant