release: update LiteParse to 2.13.1 - #233
Merged
Advait Paliwal (advaitpaliwal) merged 2 commits intoAug 17, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Advait Paliwal (advaitpaliwal)
deleted the
codex/liteparse-2.13.1-0.3.26
branch
August 17, 2026 09:33
Contributor
Author
|
Release receipt for
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
LiteParse 2.13.1 fixes table extraction that dropped in-table cells between established columns in multi-line headers. This directly improves paper and document reading.
Upstream evidence:
2856997c018c04cfde568e306d40de0fa0ca9f61.31996133977published the wrapper and seven native packages.Detail,X,Y, andZon 2.13.0 and preserves all four on 2.13.1.What changed
createRequirefor Node 22 compatibility.es-module-lexer@2.3.1; no unrelated runtime dependency drift remains.--save-exact.Node 22 repair
The first candidate run,
32007231665, failed its Node22.22.0consumer because the installed runtime silently resolved LiteParse2.10.1.The packaged archive had been built on Node 24. Node 22 rejected its ABI manifest, so
patch-embedded-pi.mjsrestored the archive. The installer then replacedfeynman-runtimewith only six fallback packages. That dropped the archive overrides and letpi-docparserinstall its old transitive LiteParse.Commit
45bab8ffixes the owning installer instead of adding a consumer fallback.Verification
Exact head:
45bab8fcb6c142080973b9646d28c7378b1b4c56Local:
efcb79007257a04466c7308c1cf9660075513b1512287a87b6c22ec9e6f4ff55.22.22.0local/global consumers passed package, stale-Pi, 15-tool/9-command RPC, TypeBox, extension, document parse/search/screenshot, and four-column table checks.Daytona sandbox
880d5d13-9aa0-4a9b-9370-d050009d4545:25.9.0plus typecheck, build, architecture, website lint/typecheck/build, root/site audits, freshness review, and diff checks.24.18.0dry and real Linux packs matched at 116,546,653 bytes, 300,604,747 unpacked bytes, and 29,138 files; SHA-256cbc36c7e187ff12437da2fa03b2e9dbe82e4b18e81bccb02e3c9e5552b2c5edf.22.22.0local and global consumers passed zero-vulnerability audits and all package/runtime/document gates.2.13.1, Pi0.84.2, and Undici8.10.0from the Node 24 archive.cbc36c7e187ff12437da2fa03b2e9dbe82e4b18e81bccb02e3c9e5552b2c5edf.Exact-head GitHub run
32011538818passed the release candidate, Windows installer, and all six supported Node/OS consumer jobs.