v1.7.2

Starlake 1.7.2 (maintenance release)

Bug fix

• OVERWRITE transforms insert by name, never by position (#1722): overwriting an existing table used a positional INSERT on most engines, so a SELECT whose column order diverged from the table's could silently write every value into the wrong column, or fail with a confusing count/cast error. All engines now pass the explicit column list resolved from the SELECT: values land in the columns of the same name regardless of SELECT order, and a column the table does not have fails loudly with a clear message. If you use OVERWRITE transforms on the 1.7 line, upgrading is strongly recommended.

Improvements (backported from 1.8.2)

• Actionable schema-mismatch errors: when a transform fails because the SELECT returns columns the target table lacks, the error names the missing columns and prints the exact commands that fix it (starlake transform --name <task> --sync-apply, then re-run).
• Automatic SQL-to-YAML sync (opt-in): with SL_SYNC_SQL_WITH_YAML=true, a transform aligns the task's YAML attributes with its SQL before running. Off by default because it rewrites .sl.yml files in your project.

What's Changed

• backport(1.7): OVERWRITE inserts by name, sync-apply hint, syncSqlWithYaml by @hayssams in #1725

Full Changelog: v1.7.1...v1.7.2