Skip to content

v4.2.2 — CLI batch fix + retraction docs

Choose a tag to compare

View all tags
@mysleekdesigns mysleekdesigns released this 18 May 05:00
· 53 commits to main since this release
v4.2.2
a3e1ff6

Highlights

  • Fixes crawlforge batch CLI command — user-supplied --format, --concurrency, and --max-retries flags were silently dropped because the command passed output_format / concurrency / max_retries to BatchScrapeTool.execute(), but BatchScrapeSchema expects formats / maxConcurrency / jobOptions.maxRetries. Zod's strip-mode discarded the unknown keys so the tool ran with defaults regardless of CLI args. Now maps to the schema's actual keys, and a contract test pins the param shape.
  • CHANGELOG v4.0.0 retracted — the v4.0.0 "breaking change" to `batch_scrape` defaults was a phantom at the MCP surface (the MCP registration always defaulted to `['json']`; only the inner schema mismatched). v4.2.1 fixed the inner schema; v4.2.2 now ships the corrected CHANGELOG to npm.
  • CI workflow fixed (internal — not in tarball): quoted glob `"tests/unit/*.test.js"` never expanded, so unit-tests job failed in 0s with "Could not find". Replaced with `find`-expanded args, added `--test-force-exit` to bypass legacy D2 open-handle hangs, bumped CI Node 20 → 22. Now runs 417 tests across 18 files in ~14s.

Install / upgrade

```bash
npm install -g crawlforge-mcp-server@4.2.2
```

Verification

  • 11/11 batchScrape unit tests pass (including new contract test)
  • 6/6 CLI integration tests pass
  • 417/417 tests pass in CI in ~14s with `--test-force-exit`
Assets 2
Loading