Minor Branch Checklist

Micronaut follows semantic versions. When working on a new feature, your PR base branch should be the next minor version of the module.

If the minor branch does not exist, you can create it. Create a new branch of the previous one. Imagine you are working on branch 1.4.x.

• Create 1.5.x branching of 1.4.x
•  Edit grade.properties. Set projectVersion to 1.5.0-SNAPSHOT.
•  Commit and push. You could skip ci with a commit message such as: ci: projectVersion=1.5.0-SNAPSHOT [ci skip]
• Set the default branch to the next minor branch. If you don't have access, ask Graeme or Sergio to do that.