What dbcli/pgcli shipped
Written by FoxPlug from public releases; not affiliated with Pgcli. An automatic summary of the public release, pull request and commit data of github.com/dbcli/pgcli. Pgcli did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
Week of September 14, 2026
What shipped
- Released version 4.7.1 to fix the version number display in pgcli --version. Release
- Released version 4.7.0 with support for running SQL commands directly from the command line using -c or --command options, which can be specified multiple times and combined with -f. Release
- Fixed destructive command detection to use sqlparse instead of whitespace splitting, preventing false negatives when string literals contain the word 'where'. Pull request #1614
- Marked
test_execute_statements_does_not_split_inside_literalswith @dbtest decorator so it skips when no local postgres database is available. Pull request #1643
Why it matters
Version 4.7.0 brings new command-line functionality for running SQL statements directly, and 4.7.1 fixes a reporting bug. A critical fix improves the safety of destructive command warnings by using proper SQL parsing instead of text splitting.
Changelog entry
- 4.7.1: Fixed version number display in pgcli --version Release
- 4.7.0: Added -c/--command options to run SQL commands directly from command line Release
- Fixed destructive command detection to use sqlparse instead of whitespace splitting Pull request #1614
pgcli 4.7.1 is out, fixing the version display. 4.7.0 added -c/--command support for running SQL from the CLI, plus improved destructive command detection.
pgcli 4.7.1 is released with a bug fix for version reporting. The 4.7.0 release brought command-line support for executing SQL statements with -c/--command options, and improved safety checks for destructive commands by switching to proper SQL parsing for detection.