Breaking changes information missing from ChangeLog

Upgrading from SeaORM 0.12 to 1.1

There seem to be some changes that are breaking changes but aren't mentioned in the Changelog, which tripped me up during an upgrade. It would be helpful to expand the information in the ChangeLog for others.

1. The requirement to always define an ActiveModel for a table. In v0.12 I did not implement ActiveModel for some tables because they are read-only, managed directly by some database triggers. In this instance SeaORM defines the schema and I wanted a compile error should somebody try to write code to update the rows.

error[E0412]: cannot find type `ActiveModel` in this scope
 --> table.rs:5:39
  |
5 | #[derive(Copy, Clone, Default, Debug, DeriveEntity)]
  |                                       ^^^^^^^^^^^^
  |
  = note: this error originates in the derive macro `DeriveEntity` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing one of these items

I see it's now written in the doc here that it should always be defined: https://www.sea-ql.org/SeaORM/docs/generate-entity/entity-structure/

2. ColumnType::String definitions seem to have changed, wrapped by StringLen.
   ColumnType::String(Some(32)).def()

3. use sea_orm::sea_query::BlobSize has been Dropped, but no indication of what it should have been replaced with.

I guess that ColumnType::Binary(BlobSize::Blob(None)).def() should be ColumnType::Binary(0).def()

ColumnType defines:

    Binary(u32),
    VarBinary(StringLen),

On PostgreSQL should I now be using ColumnType::VarBinary(StringLen::None) or ColumnType::Binary(0).def() or does it matter?

Review the ChangeLog and the linked entity-structure documentation, then compare the listed SeaORM 0.12-to-1.1 changes: ActiveModel requirements, ColumnType::String, and BlobSize removal. Done means the Changelog clearly records each breaking change and explains the replacement or current API choice where the issue raises alternatives.