Skip to content

fix(deps): bump libpg-query to 18.2.1 and @pgsql/parser to ^1.6.2 - #363

Merged
pyramation merged 2 commits into
mainfrom
devin/1792896940-libpg-query-18-2-1
Oct 25, 2026
Merged

pyramation merged 2 commits into
mainfrom
devin/1792896940-libpg-query-18-2-1

Conversation

@pyramation

@pyramation pyramation commented Oct 25, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

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.
  • @pgsql/parser 1.6.2 bundles the same six WASMs and fixes ESM import in Node. Every earlier 1.x threw ERR_UNSUPPORTED_DIR_IMPORT on ./types (fix(parser): ESM entry points fail with ERR_UNSUPPORTED_DIR_IMPORT libpg-query-node#181).

config/versions.json is left unchanged, as in #362. Only the 18 line gets republished.

The lockfile diff only touches libpg-query and @pgsql/parser. I ran prettier on it to keep the repo's double-quoted lockfile style.

Local verification: pnpm run build passes. pnpm test passes in parser, deparser, transform-ast (1443 tests), plpgsql-parser and lint.

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

@devin-ai-integration

Copy link
Copy Markdown
Contributor

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

  • Disable automatic comment, CI, and merge conflict monitoring

@tenki-reviewer

tenki-reviewer Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

Review complete. No issues found — approved ✅.


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.

Files Change
packages/{parser,deparser,lint,parse,pgsql-types,plpgsql-deparser,plpgsql-parse,plpgsql-parser,transform-ast}/package.json 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.

Reviewed commit: 5c0cc33

@socket-security

socket-security Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedlibpg-query@​18.2.0 ⏵ 18.2.110010010096 +1100

View full report

@devin-ai-integration devin-ai-integration Bot 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
@pyramation
pyramation merged commit 8ac1a45 into main Oct 25, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant