For some reason, migration 7bb5891a9f2e_lowercase_email.py is not being called on new db creations, that is why the citext extension wasn't created and devs were encountering errors
This would most probably be due to some merge conflict and erroneous linking to previous migration. In this way, multiple migrations may have been knocked out of the chain.
This was called on production DB, so we need to think of a way to reintroduce orphan migrations without breaking the production DB
Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.95. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
@uds5501 Why was this closed?
Output of 'python3 manage.py db history'

Create a new database and run migrations and see
@iamareebjamal Oh ya.
@iamareebjamal Created a new database.

Strange. Closing
Most helpful comment
Issue-Label Bot is automatically applying the label
bugto this issue, with a confidence of 0.95. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!Links: app homepage, dashboard and code for this bot.