We are using fly for DB migration. We are assigning the version number while merging with main branch. There will be a conflict when other developer uses the same version there will be a conflict and second person need to assign new number and merge with main branch. Is there a better process (automated process) to assign unique version number.

We are using Flyway for DB migration as part of CI/CD process.
We are creating a new file with latest version number while merging with main branch. There will be a conflict when other developer uses the same version there will be a conflict and second person need to create a new file with updated Version number and merge with main branch.
Is there a better process (automated process) to assign unique version number?

We are using Flyway for DB migration as part of CI/CD process.
We are creating a new file with latest version number while merging with main branch. There will be a conflict when other developer uses the same version there will be a conflict and second person need to create a new file with updated Version number and merge with main branch.
Is there a better process (automated process) to assign unique version number?

We are using Flyway for DB migration as part of CI/CD process.
We are creating a new file with latest version number while merging with main branch. There will be a conflict when other developer uses the same version there will be a conflict and second person need to create a new file with updated Version number and merge with main branch.
Is there a better process (automated process) to assign unique version number?

We are using Flyway for DB migration as part of CI/CD process.
We are creating a new file with latest version number while merging with main branch. There will be a conflict when other developer uses the same version there will be a conflict and second person need to create a new file with updated Version number and merge with main branch.
Is there a better process (automated process) to assign unique version number?

We are using Flyway for DB migration as part of CI/CD process.
We are creating a new file with latest version number while merging with main branch. There will be a conflict when other developer uses the same version there will be a conflict and second person need to create a new file with updated Version number and merge with main branch.
Is there a better process (automated process) to assign unique version number?

We are using Flyway for DB migration as part of CI/CD process.
We are creating a new file with latest version number while merging with main branch. There will be a conflict when other developer uses the same version there will be a conflict and second person need to create a new file with updated Version number and merge with main branch.
Is there a better process (automated process) to assign unique version number?

We are using Flyway for DB migration as part of CI/CD process.
We are creating a new file with latest version number while merging with main branch. There will be a conflict when other developer uses the same version there will be a conflict and second person need to create a new file with updated Version number and merge with main branch.
Is there a better process (automated process) to assign unique version number?

In Flyway documentation I found that it supports migration script not only in SQL format, but also as PowerShell, Bash, Python etc. formats (Flyway docs)

My Environment build.gradle.kts plugins { java id(“org.springframework.boot”) version “3.3.1” id(“io.spring.dependency-management”) version “1.1.5” id(“com.diffplug.spotless”) version “6.25.0” id(“io.freefair.lombok”) version “8.6” id(“jacoco”) id(“org.flywaydb.flyway”) version “10.16.0” } group = “com.wesang.walletyo” version = “0.0.1” java.sourceCompatibility = JavaVersion.VERSION_17 configurations { runtimeOnly { exclude(group = “commons-logging”, module = “commons-logging”) } } flyway { url = “jdbc:mysql://localhost:3310” user = “walletyo_user” password = “walletyo_password” […]