In this case, we need to add nullable column first, then fill the column with unique values somehow. Or create a new table with an auto-incremented unique-id column and copy records from the existing table.
Since we already published 4.35.0, we cannot update 4.35.0 released artifacts. We should release 4.35.1 (or 4.36.0) with a fix for this issue.
@takezoe thanks for working on this issue. And I’m sorry for this bug... i didnt notice because i tested on only empty table. And maybe it might be better if gitbukcet migration test consider non empty table migration.
Right, but I know covering existing records cases would be annoying. I wonder if we could find an automated solution for that.
Or simply checking the existence of adding non-null columns without default value in migration scripts might work.