On Thu, Oct 16, 2025 at 4:42 PM Andrew Lamb <[email protected]> wrote:
> +1 (binding) > verified on M3 mac > > One thing I noticed was the changelog [1] lists a "breaking change" > > > Unify Table representations #1256 (timsaucer) > > Is it a problem to release a breaking change in a minor release? > > Andrew > > Thanks, Andrew. I think this is erroneously marked as breaking. We have deprecated one API and that was marked as API change which shows up as breaking in the changelog. I just reviewed the user facing API changes. They are all backwards compatible, except with a deprecation warning. I am also comfortable making a new release candidate without this PR.
