Skip to content

Module Release

Jump to bottom
Sergio del Amo edited this page Jun 12, 2025 · 3 revisions

Before publishing the release, verify that you are using the correct branch. If you are adding features to a module, it should be a minor module release as we follow semantic versioning. Create a minor branch for the module.

Before doing a module release, we recommend you align it with the platform BOM the module targets.

Once you have a branch ready to be released, follow this steps:

  • Create a release
  • Select the branch you are releasing. DOUBLE CHECK THIS!
  • Choose a tag. The tag should start with v. For example, if you are doing the first release of the 4.9.x branch, you will use the v4.9.0 tag.
  • Click the Generate Release Notes button. This button action populates the release's description. PRs included in the description are organized into categories based on the PR labels.
  • Verify GitHub Status is Operational https://www.githubstatus.com
  • Verify Sonatype is Operational https://status.maven.org
  • Verify Gradle Status https://status.gradle.com/
  • Click Publish Release.
  • Monitor the GitHub Action Release to verify if the release process is successful.
Clone this wiki locally