When I update the version from 3.3.3 to 3.4.1 and set column not null which has null values, an exception is reported.

When executing the SQL ALTER TABLE t_message MODIFY COLUMN status INT(11) NOT NULL DEFAULT '0' with the mariadb-java-client version 3.3.3, no error occurs even if the status column contains NULL values. However, the same SQL throws an error (State: 22004, Error Code: 1138) in version 3.4.1. Notably, executing this SQL directly in the MySQL database also doesn't produce an error, all under the condition that the column contains NULL values.What changes were made between versions 3.3.3 and 3.4.1 that caused this exception to occur?

I've found the changes.