v4.5.0

Support for Liquibase 4.5.0.

v4.4.3

Support for Liquibase 4.4.3.

v4.4.2

Support for Liquibase 4.4.2.

Bugfixes
This release fixes a long-standing issue that caused Liquibase operations against non-Mongodb databases to fail if the liquibase-mongodb.jar was in the classpath.

Starting with this release, you can safely keep this extension in your classpath regardless of what database you are working against.

v4.4.1

Support for Liquibase 4.4.1.

Known Issue: Including this extension in your classpath will impact your ability to run Liquibase against non-Mongodb databases. This has been fixed in liquibase-monogodb 4.4.2

v4.4.0

Support for Liquibase 4.4.0.

Known Issue: Including this extension in your classpath will impact your ability to run Liquibase against non-Mongodb databases. This has been fixed in liquibase-monogodb 4.4.2

v4.3.5

Support for Liquibase 4.3.5.

Known Issue: Including this extension in your classpath will impact your ability to run Liquibase against non-Mongodb databases. This has been fixed in liquibase-monogodb 4.4.2

v4.3.4

Support for Liquibase 4.3.4.

v4.3.3

Support for Liquibase 4.3.3.

v4.3.2

Support for Liquibase 4.3.2.

v4.3.1.1

• Upgrade Mongo Java Driver from 4.2.1 to 4.2.2
• Fixed #111: Is adminCommand really connected to the admin DB?

Thank you to @DarrinProtag and @jsonking.