Did you read the line underneath?

Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.

Sounds like its just a strong warning that they'll change their APIs when they want (in the name of security). Not that it isn't production ready.