Hi.. I recently updated to SqlCL 26.1… This is my changelog

However.. when deployed to production, this changed my identity column to start with 1611.. in production, I was already over 2000.. so my users got PK errors. Fortunately, for this update, I only had a few tables, so I was able to increase the sequences properly.
Reverting back to 25.4.2, this still seems to happen. Is there a command to avoid this when updating a table? Or is this a bug?