After upgrading my Spring Boot app from Spring Boot 3.4.1 to 3.5.3 which brings Liquibase 4.31 into the game, there is an issue regarding the context match.
I use contexts (ci, testdata) in my changelog.xml but the most changesets are defined without any specific context, which means, those changeset are declared for the default context.
The application.yml for the Spring Boot profile used for production contains the following liquibase context definition:
liquibase:
enabled: true
drop-first: false
contexts: default,!zeiterfassung_fair,!ci # !testadta
This means, deploy only changesets declared for default context (all changesets without any certain context) and those who ar NOT in context ‘ci’ and NOT in context ‘zeiterfassung_fair’. The last part after the ‘#’ is only a comment in the yml file.
After upgrade my Spring Boot app, all changesets declared for context ‘ci’ are deployed too, which differs from behavior before upgrading.
Is this a bug ?
Kind regards
Dominik