Camunda liquibase migration

Hello.

I have spring boot module with dependencies (starter) for Camunda.
On production we have several microservices which consumes this common module.
Also, this microservices have liquibase migration, but it’s empty:

SELECT * FROM databasechangelog;
0 rows;

Then i updated camunda engine version from 7.10 to 7.11. So, there are some changes in SQL.

So, my next assumption is next: i want to add this script in this common module with preconditions.
Something like that:

--preconditions onFail:CONTINUE onError:CONTINUE
ALTER TABLE ACT_HI_OP_LOG
    ADD CATEGORY_ VARCHAR(64);

--preconditions onFail:CONTINUE onError:CONTINUE
ALTER TABLE ACT_HI_OP_LOG
    ADD EXTERNAL_TASK_ID_ VARCHAR(64);

--preconditions onFail:CONTINUE onError:CONTINUE
CREATE TABLE ACT_GE_SCHEMA_LOG
(
    ID_        VARCHAR(64),
    TIMESTAMP_ timestamp,
    VERSION_   VARCHAR(255),
    PRIMARY KEY (ID_)
);

--preconditions onFail:CONTINUE onError:CONTINUE
INSERT INTO ACT_GE_SCHEMA_LOG
VALUES ('0', CURRENT_TIMESTAMP, '7.11.0');

--preconditions onFail:CONTINUE onError:CONTINUE
CREATE INDEX ACT_IDX_HI_OP_LOG_USER_ID ON ACT_HI_OP_LOG (USER_ID_);

--preconditions onFail:CONTINUE onError:CONTINUE
CREATE INDEX ACT_IDX_HI_OP_LOG_OP_TYPE ON ACT_HI_OP_LOG (OPERATION_TYPE_);

--preconditions onFail:CONTINUE onError:CONTINUE
CREATE INDEX ACT_IDX_HI_OP_LOG_ENTITY_TYPE ON ACT_HI_OP_LOG (ENTITY_TYPE_);

Is such an idea correct for each consumer of common starter?