Forcibly convert to utf8mb4 when upgrading from 1.7?

[yelto]

In 2.0 the db is all utf8mb4, but I can't see where support/scripts/update_database_to_utf8mb4.sh is triggered, or where the user is prompted to do run it.

[collectiveaccess]

It must be done manually. Things will work fine with older encodings, so long as mb4 characters are not used (they are rarely used in archives work).

[yelto]

Ok, not an issue then since there is no intent to have all 2.0 dbs fully at utf8mb4. Without prompting most 1.7 upgrades will probably be mixed encoding (but mostly mb3) and miss out on all those emojis...