liquibase: Inconsistent changelog filename after updating to 4.3.1

Environment

Liquibase Version: 3.10.2 -> 4.3.1 Liquibase Integration & Version: Spring Boot 2.4.3 Liquibase Extension(s) & Version: - Database Vendor & Version: AWS Aurora Operating System Type & Version: -

Description

After upgrading Liquibase from version 3.10.2 to 4.3.1, the logic of calculating the FILENAME column value of each changelog in the DATABASECHANGELOG table is different. Because the filename is a part of the changelog’s identifier, this causes all of the previously executed changelogs to run again.

Before the update, there were some entries in the DATABASECHANGELOG table that looked like so:

ID,AUTHOR,FILENAME
id1,author,db/changelog/changesets/1.yaml
id2,author,db/changelog/changesets/2.yaml

After the update, these changelogs were executed again, adding new DATABASECHANGELOG entries. This is the result:

ID,AUTHOR,FILENAME
id1,author,db/changelog/changesets/1.yaml
id2,author,db/changelog/changesets/2.yaml
id1,author,BOOT-INF/classes/db/changelog/changesets/1.yaml
id2,author,BOOT-INF/classes/db/changelog/changesets/2.yaml

Steps To Reproduce

• Use db.changelog-master.yaml with content:

databaseChangeLog:
  - includeAll:
      path: db/changelog/changesets

• Use Liquibase 3.10.2
• Create a Spring Boot JAR file and run it
• Changelogs are executed for the first time
• Upgrade to Liquibase 4.3.1
• Re-create the Spring Boot JAR and run it again
• Previously executed changelogs are executed for the second time

Actual Behavior

Changelogs which have been previously executed are executed again.

Expected/Desired Behavior

None of the previously executed changelogs are executed again.

Screenshots (if appropriate)

Parts of the DATABASECHANGELOG table content after running Liquibase 4.3.1 (notice the same MD5 sum for the first and last four changelogs - those are the changelogs that have been executed again):

┆Issue is synchronized with this Jira Story by Unito