Migrating project from Jmix 1.4.4 to Jmix 1.5.0 fails with Liquibase class error

I just tried to upgrade my Jmix 1.4.4 project to different versions of Jmix 1.5 and I keep getting the following Migration failure:

Migration failed: java.lang.ClassCastException: class com.haulmont.jpb.liquibase.dom.IncludeFile$$EnhancerByJetBrainsMainCglib$$709fff99 cannot be cast to class com.haulmont.jmixstudio.liquibase.dom.IncludeFile (com.haulmont.jpb.liquibase.dom.IncludeFile$$EnhancerByJetBrainsMainCglib$$709fff99 is in unnamed module of loader com.intellij.ide.plugins.cl.PluginClassLoader @5cec8707; com.haulmont.jmixstudio.liquibase.dom.IncludeFile is in unnamed module of loader com.intellij.ide.plugins.cl.PluginClassLoader @3437bb9b) To avoid project inconsistent state, please revert all changes made during unsuccessful migration attempt. You can use Edit > Undo Migrate Project, Local History or VCS to perform revert.

I updated to the latest version of Jmix Studio as well:

IntelliJ IDEA 2023.2.5 (Ultimate Edition)
Build #IU-232.10227.8, built on November 9, 2023
Licensed to Eric Raskin
Subscription is active until May 3, 2024.
Runtime version: 17.0.9+7-b1000.46 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0
GC: G1 Young Generation, G1 Old Generation
Memory: 3192M
Cores: 8
Registry:
editor.minimap.enabled=true

Non-Bundled Plugins:
org.intellij.plugins.hcl (232.8660.88)
com.intellij.properties.bundle.editor (232.8660.88)
org.jetbrains.kotlin (232-1.9.21-release-633-IJ10072.27)
com.intellij.gwt (232.10227.8)
com.intellij.lang.jsgraphql (4.0.2)
org.mapstruct.intellij (1.6.1)
com.haulmont.jpab (2023.4.1-232)
CUBA (15.10-232)
com.dmarcotte.handlebars (232.8660.88)
Pythonid (232.10227.8)
com.intellij.bigdatatools.core (232.10227.8)
com.intellij.bigdatatools.binary.files (232.10072.27)
com.intellij.bigdatatools.rfs (232.10227.8)
com.google.gct.core (23.10.2-api-version-222)
io.jmix.studio (2.1.1-232)

Kotlin: 232-1.9.21-release-633-IJ10072.27

Any suggestions on what to do next?

Hi

Seems that this is JPA Buddy compatibility issue. Please disable JPA Buddy plugin and try migration once again.

We’ll check and try to fix the issue on our side in the following releases.

Thank you.