Figure out why latest deployment is pending

[cisaacstern]

As noted in the comment there, I meant to wait to merge #3 until new features on the backend would prevent a production run from being triggered by that PR. I go a bit confused, however, and forgot to wait! (The backend features were added, but not deployed to the production backend yet.)

I had not intended to deploy a production run following merge of #3, but since it did happen unintentionally, I'm not clear why it was left in a pending state. This will require some further investigation.