Skip to content

chore(deps): bump sqlparse from 0.5.5 to 0.6.0 #536

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps): bump sqlparse from 0.5.5 to 0.6.0 #536

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion setup.cfg
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ install_requires =
pydantic>=2.13.5,<3.0.0
python-dateutil>=2.9.0.post0
readerwriterlock>=1.0.9
sqlparse==0.5.5
sqlparse==0.6.0

@cursor cursor Bot Oct 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 8751784. Configure here.

trio>=0.31.0
truststore>=0.10.4
python_requires = >=3.10
Expand Down
Loading