Semantic versioning / breaking changes in CHANGELOG

[mistercrunch]

Hey friends. First I wanted to point out we're making great use of sqlglot in Apache Superset and it'd been great to have a higher-level abstraction as we migrate from sqlparse, and we're most of the way through.

Recently I was bumping packages and read through https://github.com/tobymao/sqlglot/blob/main/CHANGELOG.md, and felt like many changes were maybe part of the private API (?) Found wondering if all of the labeled breaking changes actually breaking the public API? Also wondering if they could be bundled and/or less frequent.

Totally cool if the word is "yes they are all breaking and we're moving really fast right now, things should settle later on, ...", just trying to get a better sense of the dynamics in the repo/releases.

[tobymao]

breaking changes happen whenever the generation of SQL changes on valid statements. SQLMesh relies on the notion because it fingerprints SQL.

so i guess it depends on what you mean by "public api". if you're just talking python code, that doesn't change very much. so we consider it more from a SQL generation perspective.

because of how wide and vast sql is, we continue planning to release frequently quite often.