chore(deps): bump sqlparse from 0.5.5 to 0.6.0

[dependabot]

Bumps sqlparse from 0.5.5 to 0.6.0.

Changelog

Sourced from sqlparse's changelog.

Release 0.6.0 (Aug 13, 2026)

Notable Changes

• Drop support for Python 3.8 and 3.9. Python 3.10+ is now required.
• IMPORTANT: Fixes a potential denial of service attack (DOS) in the lexer, which consumed CPU quadratically on statements containing many unclosed dollar-quoted literals or multiline comments (CVE-2026-59893). See the security advisory for details: GHSA-prg7-hcfm-mfcr The vulnerability was discovered by EQSTLab, min8282 and 7thpark. Thanks for reporting!
• IMPORTANT: Fixes a potential denial of service attack (DOS) when grouping deeply nested or very wide statements. Building a token group re-read the whole group on every step, so a small statement could keep a worker busy for a long time (CVE-2026-54284, pr848 by alhudz and tonghuaroot).
• IMPORTANT: Fixes a potential denial of service attack (DOS) in format(sql, reindent=True), which consumed CPU quadratically on long lists of tuples. See the security advisory for details: GHSA-cfqr-cjx5-5jcm
• IMPORTANT: Fixes a potential denial of service attack (DOS) on statements that consist only of comments (CVE-2026-71491). See the security advisory for details: GHSA-f2ff-p2ww-7p4p The vulnerability was discovered by @​sanktjodel. Thanks for reporting!
• IMPORTANT: Backslashes are now escaped in the python and php output formats. Without escaping, SQL containing a backslash could break out of the generated string literal (CVE-2026-59894). See the security advisory for details: GHSA-3496-9g83-7v6x The vulnerability was discovered by @​7thParkk. Thanks for reporting!

Enhancements

• Modernize type annotations in top-level API functions using PEP 585 and PEP 604 syntax.
• END FOR and END CASE are now recognized as keywords.

Bug Fixes

• Statement splitting was rewritten on a stack-based architecture. This fixes splitting of statements with nested BEGIN ... END blocks (issue845).
• Fix function grouping being skipped in CREATE TABLE ... AS SELECT statements when the as keyword is lowercase (pr867 by Osamaali313).
• Recognize ROW_FORMAT as a keyword so that ALTER TABLE ... ROW_FORMAT=... no longer merges the table name and the option into a single identifier (issue773, pr860 by apoorvdarshan).
• Recognize MATERIALIZED as a keyword so it is parsed and formatted consistently in CREATE MATERIALIZED VIEW statements (issue752, pr854 by

... (truncated)

Commits

• 2f40da9 Update version number.
• 5753f15 Align the changelog entries for this release with previous ones
• b9588d9 Unify the benchmark scripts on a shared harness
• 519e416 Pair comment/dollar-quote delimiters at the lexer position
• a51df6d Measure reindent offsets backwards to avoid quadratic CPU use
• 73d9ccd Update CHANGELOG
• d1d8060 Fix uncontrolled CPU consumption (ReDoS) in the lexer's handling of dollar-qu...
• ef2012a Fix quadratic DoS in group_comments (GHSA-f2ff-p2ww-7p4p)
• 26112dd Update Changelog.
• 53ff44b Escape backslashes in output formatters.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Note

Low Risk
Single dependency pin for security patches; sqlparse is used for SQL formatting with a monkey-patched splitter, so regressions are possible but scope is limited to parsing/formatting behavior.

Overview
Pins sqlparse from 0.5.5 to 0.6.0 in setup.cfg install requirements.

This is a security-focused upstream release (multiple DoS fixes in lexing, grouping, and format(..., reindent=True)), plus parser improvements such as stack-based statement splitting and additional keyword recognition. The SDK already requires Python 3.10+, which matches sqlparse 0.6 dropping 3.8/3.9. Client SQL handling in statement_formatter depends on sqlparse parsing/grouping and applies a local patch to StatementSplitter; worth a quick pass on parameter substitution and multi-statement splitting after the upgrade.

^{Reviewed by Cursor Bugbot for commit 8751784. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8751784. Configure here.}

[cursor]

sqlparse bump breaks splitter patch

High Severity

Bumping sqlparse to 0.6.0 is incompatible with the existing monkey-patch of StatementSplitter._change_splitlevel in statement_formatter.py. That patch still reads 0.5.5 fields such as _begin_depth and _in_case, which 0.6.0 replaced with _block_stack. Parsing SQL that contains BEGIN, DECLARE, or nested CASE can raise AttributeError or split statements incorrectly.

 

^{Reviewed by Cursor Bugbot for commit 8751784. Configure here.}

[dependabot]

Looks like sqlparse is up-to-date now, so this is no longer needed.