Commits that break the SQL compiler or make non-backwards-compatible changes tend to break DBSP CI and docker workflows. The solution is to start tagging "stable" compiler releases and have DBSP point to a specific tag rather than the main branch of this repo.
Better yet, we should start using github releases to automatically create binary compiler releases that can be used in DBSP CI instead of building the compiler every time the CI pipeline runs.
Commits that break the SQL compiler or make non-backwards-compatible changes tend to break DBSP CI and docker workflows. The solution is to start tagging "stable" compiler releases and have DBSP point to a specific tag rather than the
mainbranch of this repo.Better yet, we should start using github releases to automatically create binary compiler releases that can be used in DBSP CI instead of building the compiler every time the CI pipeline runs.