Repository navigation
fix(deps): pgsql-parser 18.3.4 family, libpg-query ^18.2.4 - #1995
Conversation
…e Workers loadModule fix)
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
|
Review complete. No issues found — approved ✅. The change is a coordinated dependency-version bump of the PostgreSQL parser toolchain ( Reviewed commit: 236db15 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Summary
Downstreams the Cloudflare Workers
loadModule({ wasm })fix (libpg-query-node#194). It shipped inlibpg-query18.2.4 and reached us through pgsql-parser#377. Only the JS glue changed; the.wasm, the API and the AST are the same.npx makage deps ../pgsql-parser --installbumped 22 ranges:pgsql-parser^18.3.4,pgsql-deparser^18.4.4,plpgsql-parser^18.6.5,@pgsql/{lint,traverse,utils,scripts,semantics,transform}safegres:libpg-query^18.2.0 → ^18.2.4, so the lockfile resolves to the fixed build. makage doesn't match this one because libpg-query-node's workspace names are@libpg-query/vNN. The 18.2.0 / 18.2.1 lock entries collapse into one 18.2.4 entry.prettieronpnpm-lock.yaml;pnpm install --frozen-lockfilepasses with it.Link to Devin session: https://app.devin.ai/sessions/8ffe0c4157eb424882da48eb003e5165
Open in Devin Desktop: https://app.devin.ai/desktop/session/8ffe0c4157eb424882da48eb003e5165?variant=devin
Requested by: @pyramation