Repository navigation
chore(deps): bump pgsql-parser packages to the literal-escaping release - #1877
Merged
Merged
Conversation
…l-parser 18.2.10, plpgsql-parser 18.5.12, @pgsql/* )
Contributor
|
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 ✅. A routine dependency refresh moving the PostgreSQL parser toolchain to the latest patch releases of the 18.x line across all consuming packages. Every bump uses caret ranges so resolution stays within the compatible release train, and the versions align with what is published to the lockfile — no manifest/lockfile drift was detected.
Reviewed commit: 04198b3 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
Summary
Picks up the pgsql-parser release that includes pgsql-parser#358. In that release the TS deparser escapes quotes in string literals (bit strings, transaction gids, option values, role password/
VALID UNTIL, XMLTABLE paths, …) and rejects invalid numericfval/ivalvalues when deparsing hand-built ASTs.Generated with
makage deps ../pgsql-parser --install. It changed 21 ranges across 10 packages:pgpm/core,csv-to-pg,graphile-sql-expression-validatorpgsql-deparser ^18.3.10,pgsql-parser ^18.2.10(+@pgsql/utils ^18.2.12in csv-to-pg)pgpm/cli,pg-ast,@constructive-io/query-builderpgsql-deparser ^18.3.10node-type-registrypgsql-deparser ^18.3.10,@pgsql/utils ^18.2.12safegres@pgsql/lint ^18.2.10,@pgsql/traverse ^18.7.12,pgsql-deparser ^18.3.10,pgsql-parser ^18.2.10@pgpmjs/transform@pgsql/scripts ^18.4.10,@pgsql/semantics ^18.1.11,@pgsql/transform ^18.17.10,plpgsql-parser ^18.5.12@pgpmjs/sliceplpgsql-parser ^18.5.12pnpm-lock.yamlwas re-run through prettier so it keeps the repo's formatting. The lockfile diff only touches thepgsql/plpgsql/@pgsqlentries, andpnpm install --frozen-lockfileis clean.Tests run locally against pg 18: pg-ast, query-builder (including db tests), node-type-registry, csv-to-pg, pgpm/transform, pgpm/slice, graphile-sql-expression-validator and safegres all pass.
Link to Devin session: https://app.devin.ai/sessions/a1e43e1e9fb2494fa571e6ecb93e1067
Open in Devin Desktop: https://app.devin.ai/desktop/session/a1e43e1e9fb2494fa571e6ecb93e1067?variant=devin
Requested by: @pyramation