This release adds 1 notable feature for engineering teams evaluating rollout.
Published 1mo
Developer Productivity
✓ No known CVEs patched
✓ No known CVEs patched in this version
Topics
document-ocr
document-processing
ocr
ocr-recognition
pdf
pdf-parser
+1 more
text-extraction
Summary
AI summaryFixed config target‑pages range expansion, search empty phrase handling, and batch‑parse output directory preservation.
Full changelog
What's Changed
- fix(config): bound target-pages range expansion to prevent OOM (#269) by @vjsai in https://github.com/run-llama/liteparse/pull/314
- fix(search): return no matches for an empty phrase by @vjsai in https://github.com/run-llama/liteparse/pull/309
- fix: preserve batch-parse output dir without trailing slash by @jjoanna2-debug in https://github.com/run-llama/liteparse/pull/313
- chore(deps): bump pypdf from 6.13.0 to 6.13.3 in /dataset_eval_utils by @dependabot[bot] in https://github.com/run-llama/liteparse/pull/321
- feat: add is_complex functionality for routing decisions by @logan-markewich in https://github.com/run-llama/liteparse/pull/318
New Contributors
- @vjsai made their first contribution in https://github.com/run-llama/liteparse/pull/314
- @jjoanna2-debug made their first contribution in https://github.com/run-llama/liteparse/pull/313
Full Changelog: https://github.com/run-llama/liteparse/compare/node-v2.1.2...wasm-v2.2.0
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About LiteParse v2
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]