Skip to content

Micronaut Core and Starter Branching Strategy

Álvaro Sánchez-Mariscal edited this page Nov 25, 2020 · 1 revision

Micronaut Core and Starter follows the same naming practices described in Micronaut Module Branch Naming.

Micronaut core's exposes always at least three branches:

  • next patch version
  • next minor version
  • next major version

Github's default branch should be pointing to next patch version.

Example scenario:

Micronaut current Patch version is 2.0.1. 2.0.x is used as a default branch for that version.

micronaut-core repo contains at least these two additional branches:

  • 2.1.x
  • 3.0.x

micronaut-liquibase module updates to Liquibase 4.x and releases a new major version. The micronaut-liquibase sets its property githubCoreBranch in gradle.properties to:

githubCoreBranch=3.0.x