Skip to content

chore: pin @libpg-query/parser to 17.7.x line#17

Merged
tianzhou merged 3 commits into
mainfrom
chore/bump-libpg-query-17.6.10
Jun 24, 2026
Merged

chore: pin @libpg-query/parser to 17.7.x line#17
tianzhou merged 3 commits into
mainfrom
chore/bump-libpg-query-17.6.10

Conversation

@tianzhou

@tianzhou tianzhou commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Pins @libpg-query/parser to the 17.7.x line.

What this changes

Moves the resolved version from 17.6.9 to 17.7.0. Uses ~17.7.0 (tilde) so the manifest allows 17.7.x patches but blocks the 18.x major — the lockfile isn't the only thing doing the pinning.

The separate 18.0.0 (pg18) major is intentionally deferred to a future task, gated on whether PG18 syntax support is needed.

Verification

  • pnpm test:parser — 25/25 ✓
  • pnpm test:autocomplete — 256/256 ✓

🤖 Generated with Claude Code

Updates to the maintainer's latest stable PG17 tag. Parser and
autocomplete test suites pass unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 24, 2026 10:41
@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pgconsole Ready Ready Preview, Comment Jun 24, 2026 10:47am

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the project’s PostgreSQL grammar/parser dependency to a newer PG17-line release by bumping @libpg-query/parser and updating the lockfile so installs use the intended version.

Changes:

  • Bump @libpg-query/parser dependency in package.json from ^17.6.9 to ^17.6.10.
  • Update pnpm-lock.yaml to resolve @libpg-query/parser to 17.6.10 (including integrity/snapshot entries).

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File Description
package.json Updates the declared dependency range for @libpg-query/parser to ^17.6.10.
pnpm-lock.yaml Updates the resolved @libpg-query/parser version and related lock entries to 17.6.10.
Files not reviewed (1)
  • pnpm-lock.yaml: Generated file

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread pnpm-lock.yaml Outdated
Comment on lines +71 to +73
'@libpg-query/parser':
specifier: ^17.6.9
version: 17.7.0
specifier: ^17.6.10
version: 17.6.10
@greptile-apps

greptile-apps Bot commented Jun 24, 2026

Copy link
Copy Markdown

Greptile Summary

This PR changes the @libpg-query/parser specifier from ^17.6.9 to ^17.6.10 and updates the lockfile accordingly. While the title describes it as a bump, the resolved version in the lockfile actually moves from 17.7.0 (what ^17.6.9 had resolved to) down to 17.6.10.

  • package.json: Specifier updated to ^17.6.10; no other dependency changes.
  • pnpm-lock.yaml: Resolved version decreases from 17.7.017.6.10, along with the corresponding integrity hash and snapshot update.

Confidence Score: 4/5

Safe to merge; the change constrains the parser to the 17.6.x grammar line and all 281 tests pass.

The resolved version moves from 17.7.0 down to 17.6.10, the opposite of what the PR title implies. This is likely intentional to stay on the PG17.6 grammar line, but the framing as a bump and absence of explicit rationale for skipping 17.7.0 is worth confirming before merging.

pnpm-lock.yaml — the resolved version change (17.7.0 → 17.6.10) is worth confirming is intentional.

Important Files Changed

Filename Overview
package.json Bumps @libpg-query/parser specifier from ^17.6.9 to ^17.6.10; no other dependency changes.
pnpm-lock.yaml Resolved version changes from 17.7.0 to 17.6.10 — the lockfile previously installed a higher minor (17.7.0) than the specifier implies; the new lock pins to exactly 17.6.10.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["package.json specifier\n^17.6.9"] -->|"pnpm resolved"| B["Locked: 17.7.0"]
    C["package.json specifier\n^17.6.10"] -->|"pnpm resolved"| D["Locked: 17.6.10"]

    B -.->|"effective change\n(downgrade)"| D

    subgraph Before["Before (main)"]
        A
        B
    end
    subgraph After["After (this PR)"]
        C
        D
    end
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["package.json specifier\n^17.6.9"] -->|"pnpm resolved"| B["Locked: 17.7.0"]
    C["package.json specifier\n^17.6.10"] -->|"pnpm resolved"| D["Locked: 17.6.10"]

    B -.->|"effective change\n(downgrade)"| D

    subgraph Before["Before (main)"]
        A
        B
    end
    subgraph After["After (this PR)"]
        C
        D
    end
Loading

Reviews (1): Last reviewed commit: "chore: bump @libpg-query/parser to 17.6...." | Re-trigger Greptile

Comment thread pnpm-lock.yaml Outdated
Use a tilde range so the manifest enforces the PG17 stable line,
not just the lockfile. Caret would still allow fresh installs to
resolve up to 17.7.x; tilde blocks 17.7.0+ while permitting 17.6.x
patches.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@tianzhou tianzhou changed the title chore: bump @libpg-query/parser to 17.6.10 chore: pin @libpg-query/parser to 17.6.x stable line Jun 24, 2026
Switch the pin from the 17.6.x stable backport to the 17.7.x line.
Tilde range allows 17.7.x patches while blocking the 18.x major.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 24, 2026 10:47
@tianzhou tianzhou changed the title chore: pin @libpg-query/parser to 17.6.x stable line chore: pin @libpg-query/parser to 17.7.x line Jun 24, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.

Files not reviewed (1)
  • pnpm-lock.yaml: Generated file

@tianzhou tianzhou merged commit 81067e7 into main Jun 24, 2026
4 checks passed
@tianzhou tianzhou deleted the chore/bump-libpg-query-17.6.10 branch June 25, 2026 03:25
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.

2 participants