Skip to content

fix(deps): pin SQLQuack 0.8.0 - #70

Closed
kvlonge wants to merge 1 commit into
mainfrom
fix/pin-sqlquack-0.8.0
Closed

kvlonge wants to merge 1 commit into
mainfrom
fix/pin-sqlquack-0.8.0

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Why

SQLQuack 0.8.0 is published with exact select-item expression ranges, which SQLBuild needs. SQLBuild links SQLClean and SQLQuack together, so SQLClean has to move to the same SQLQuack release first.

Changes

  • All six direct sqlquack-* pins in Cargo.toml move from 8d28aa4c (0.6.0) to 17088bd7 (0.8.0); Cargo.lock updates the 11 locked SQLQuack packages and nothing else.
  • No formatter, lint or fixture changes are needed: 0.7.0 and 0.8.0 don't change layout.

Verification

  • The format corpus test passes with unchanged counts for all six dialects (DuckDB 189, Snowflake 426/9 refused, BigQuery 161/7, PostgreSQL 124/13, Databricks 61/1, T-SQL 68/7), so every recorded layout still matches byte for byte.
  • cargo test --all passes (40 + 8 tests, 1 ignored as before), and cargo fmt --check and cargo clippy --all-targets -D warnings are clean.

All six direct sqlquack-* pins (11 locked packages) move from 8d28aa4c
(0.6.0) to 17088bd7 (0.8.0), so SQLBuild can link one SQLQuack copy
while taking 0.8.0's select-item expression ranges.

The formatter's output is unchanged: the format corpus formats and
refuses the same statements with the same layout in every dialect.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

Deploying sqlclean with  Cloudflare Pages  Cloudflare Pages

Latest commit: 494852b
Status:⚡️  Build in progress...

View logs

kvlonge commented Nov 12, 2026

Copy link
Copy Markdown
Contributor Author

Replaced by a PR from a kebab-case branch; the commit is unchanged.

@kvlonge kvlonge closed this Nov 12, 2026
@kvlonge
kvlonge deleted the fix/pin-sqlquack-0.8.0 branch November 12, 2026 15:38
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