Mongo-scala-driver 4.8 breaking change with RecordCodec

I am in process of upgrading 4.7 MongoDB-scala driver to 5.1 and the mentioned breaking change for v48 caught my eye - specifically regarding RecordCodec implemented in v4.6

I am not sure how this will affect folks going forward (I do have lists as parts of the database object (record) or how it will impact data already in place. If existing data will no longer be deserialized into my Scala case classes then this will be terrible news.

Maybe I am overthinking this but I find in general that terms like document, record etc are used too loosely so hard to tell.

Anyone have experience/issues with this particular breaking change?