Liquibase will automatically fail the upgrade if the database throws an error executing an SQL command. You can override the behavior with the changeSet failOnError attribute, but it defaults true which stops the database update.
If you are seeing Liquibase continue even with bad trigger SQL, your database must be allowing it to be created but then throwing runtime errors when executing it. In that case, you will need a changeSet after the create that checks the view, trigger, etc. either with a precondition or a tag that calls it.