Just took a look, and it seems to have been a mistake, and has been corrected since, it should no longer be nullable in the next RC 🙂