In order to keep up to date w/ Liquibase Core team, we need to revise the branch naming conventions and branching strategies for node-liquibase.
Liquibase Core team is making patch version releases more frequently than previously expected. In order to keep up to date on the versioned-release/* branches, we'll need to move to a branch naming convention that only lists the MAJOR.MINOR version numbers, allowing us to increment .PATCH as often as we see fit.
This will also allow us to keep up to date w/ Liquibase patch version releases.
tabuckner
commented
3 years ago 
Context
Node-Liquibase Version
ALL
Liquibase Version (if not bundled)
Description
In order to keep up to date w/ Liquibase Core team, we need to revise the branch naming conventions and branching strategies for
node-liquibase.Liquibase Core team is making patch version releases more frequently than previously expected. In order to keep up to date on the
versioned-release/*branches, we'll need to move to a branch naming convention that only lists theMAJOR.MINORversion numbers, allowing us to increment.PATCHas often as we see fit.This will also allow us to keep up to date w/
Liquibasepatch version releases.