The free version was not updated until today, unfortunately. Apologies again for the annoyance.

I've made a change to our build process that will make this error not happen ever again in the future. Thank you all again for you patience.

This issue is fixed in 2.7.9, which is now available to both Pro and free users.