Just to clarify, things work perfectly if you use "update". But NOT with "updateSQL". The SQL generated from "updateSQL" is technically invalid for oracle clients (SQL Plus, SQL Developer, others). If you were to run the attached .sql file it would actually append the UPDATE DATABASECHANGELOG lines to the bottom of the add_all_synonyms procedure which causes it to fail to compile.
When printing out the SQL of a procedure for an Oracle DB it needs to look like this:
do something, etc...;
With the slash on its own line.
Right now this is basically a blocker for us since it can easily break procedures and triggers we create. A broken one of those means an outage in our production environment