@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.