You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(deps): bump libpg-query to 18.2.1 and @pgsql/parser to ^1.6.2 - #363
Moves every package from libpg-query 18.2.0 to 18.2.1, and moves @pgsql/transform-ast from @pgsql/parser^1.5.0 to ^1.6.2.
Why:
libpg-query 18.2.1 starts the parser's WASM memory at 40 MiB instead of 128 MiB. The 32 MiB stack and the 1 GiB cap are unchanged, and the heap still grows on demand. Idle Node external memory drops from about 133 MiB to about 43 MiB per process that loads the parser. Output is unchanged: same parse trees, same errors, same speed.
Bumps libpg-query from 18.2.0 to 18.2.1 across every package manifest in the monorepo, plus a matching @pgsql/parser devDependency bump in transform-ast.
Bump libpg-query to 18.2.1 (and @pgsql/parser devDep)
pnpm-lock.yaml
Regenerated to match the 18.2.1 bump — no manifest/lockfile drift
One consistency gap was noted but not included as an inline finding: config/versions.json still pins libpg-query at 18.1.5 for the PG18 entry, which prepare-versions.ts consumes when generating the pg18 dist-tag subpackages. If the 18.2.1 bump is intended to apply to that release line too, that entry should be updated in a follow-up.
devin-ai-integrationBot
changed the title
fix(deps): bump libpg-query to 18.2.1 and @pgsql/parser to ^1.6.1
fix(deps): bump libpg-query to 18.2.1 and @pgsql/parser to ^1.6.2
Oct 25, 2026
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
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.
Summary
Moves every package from
libpg-query18.2.0 to 18.2.1, and moves@pgsql/transform-astfrom@pgsql/parser^1.5.0to^1.6.2.Why:
libpg-query18.2.1 starts the parser's WASM memory at 40 MiB instead of 128 MiB. The 32 MiB stack and the 1 GiB cap are unchanged, and the heap still grows on demand. Idle Nodeexternalmemory drops from about 133 MiB to about 43 MiB per process that loads the parser. Output is unchanged: same parse trees, same errors, same speed.@pgsql/parser1.6.2 bundles the same six WASMs and fixes ESMimportin Node. Every earlier 1.x threwERR_UNSUPPORTED_DIR_IMPORTon./types(fix(parser): ESM entry points fail with ERR_UNSUPPORTED_DIR_IMPORT libpg-query-node#181).config/versions.jsonis left unchanged, as in #362. Only the 18 line gets republished.The lockfile diff only touches
libpg-queryand@pgsql/parser. I ranprettieron it to keep the repo's double-quoted lockfile style.Local verification:
pnpm run buildpasses.pnpm testpasses inparser,deparser,transform-ast(1443 tests),plpgsql-parserandlint.Link to Devin session: https://app.devin.ai/sessions/bcd8b2f791164247acb7a659b481efc2
Open in Devin Desktop: https://app.devin.ai/desktop/session/bcd8b2f791164247acb7a659b481efc2?variant=devin
Requested by: @pyramation