MongoCK 5.4.0 does not execute change sets by order

[Qi Shen(Daniel)]

Description

we migrate from v2 to v5, now we have

• legacy change sets with deprecated annotation @ChangeLog and @Changeset , the order is from 001 to 126.

• new change sets with new annotation @ChangeUnit , the order is starting from 127.

the new change sets were always executed before legacy change sets when executing all change sets against a fresh mongodb.

PRIORITY

CRITICAL

Version and environment

Mongock

• Mongock version: 5.4.0
• Modules involved(springboot, standalone, MongoDB, DynamoDB, etc.):
  io.mongock:mongock-springboot-v3:5.4.0
  io.mongock:mongodb-springdata-v4-driver:5.4.0
• How Mongock is used: we are migrating from v2 to v5. we keeped legacy change sets with deprecated @ChangeLog and @Changeset, and we use @ChangeUnit for new change sets. Now we want to execute all change sets to setup a fresh mongo

Environment

• Framework and libraries versions. Especially those that affect directly to Mongock(Spring, Spring data, MongoDB driver, etc.)
• Infrastructure: Kubernetes, Docker, SO, etc.

Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

Behaviour

Expected behavior: [What you expect to happen]

Actual behavior: [What actually happens]

How often the bug happens: [What percentage of the time does it reproduce?]

Link to repository using Mongock

[While not mandatory, accessing to the real code that uses Mongock, would help to solve the issue]

Additional context

[Any additional information, logs, screenshots, configuration or data that might be necessary to reproduce or understand the issue]

[Qi Shen(Daniel)]

close it, fixed by add order to @ChangeLog(order = "001")