chore(deps): bump firecrawl SDK to 4.50.0 and release 3.33.3

Merged
ER
4h ago
+22-11

Moves the firecrawl JS SDK pin from 4.49.1 to 4.50.0 and releases 3.33.3, which also publishes the two crawl fixes merged since 3.33.2 (#570, #572).

SDK 4.50.0. The release lets the SDK load in browser bundles and on Node 18 and 20, and makes v2 requests work on Cloudflare Workers. The server runs on Node and uses none of those paths, so its behavior is unchanged. The lockfile diff is the firecrawl entry alone.

Engines stay at Node 22. The SDK's floor dropped to 18, but the server's own dependency tree still requires 22: mcp-proxy pulls pipenet, which needs 22+, and undici 7 (a direct dependency) needs 20.18.1+, which alone rules out 18. The changelog says so.

Release. package.json, server.json and gemini-extension.json move to 3.33.3, with a CHANGELOG entry covering the SDK bump and the crawl fixes. Merging publishes through the existing workflow.

Verified. pnpm test: 196 pass, 0 fail. tsc --noEmit clean. A stdio smoke test against the live API reports server 3.33.3 with 28 tools; firecrawl_search and firecrawl_scrape (https://example.com, markdown) both return results with no error.

Open in Capy

Summary by cubic

Bumps the firecrawl SDK from 4.49.1 to 4.50.0 and releases 3.33.3, which also publishes the two crawl fixes merged since 3.33.2.

Release 3.33.3 changes

  • firecrawl_crawl with a wait now keeps polling through rate-limited (429) status reads instead of failing, and reads result pages only once the crawl ends.
  • firecrawl_crawl now relays the API's reason, status, and code when it refuses to start a crawl.
  • Version bumps in package.json, server.json, and gemini-extension.json, plus a CHANGELOG entry.

SDK 4.50.0

  • The server behavior is unchanged: the new SDK's browser and Node 18/20 support isn't used, and the server still requires Node 22 due to mcp-proxy's pipenet dependency.