Context: my understanding is that in prep for upgrading Django, the pontoon team "squashed" a bunch of previous migrations into a single migration. The commit above is where the squashed migration is introduced, but the previous ones haven't been removed yet, so we need to deploy that commit to get our db current with the squashed ones, before we can deploy any subsequent commits where the previous migrations have been removed from the codebase.
Before updating to the latest upstream/master, we need to deploy be74890 on our instance in order to run migrations that will then be squashed. See: https://github.com/mozilla/pontoon/pull/1591#issuecomment-605656607
Context: my understanding is that in prep for upgrading Django, the pontoon team "squashed" a bunch of previous migrations into a single migration. The commit above is where the squashed migration is introduced, but the previous ones haven't been removed yet, so we need to deploy that commit to get our db current with the squashed ones, before we can deploy any subsequent commits where the previous migrations have been removed from the codebase.