Skip to content

Latest commit

 

History

History
28 lines (21 loc) · 2.17 KB

RELEASING.md

File metadata and controls

28 lines (21 loc) · 2.17 KB
Raw

Release Process

These are the steps to release Gradle profiler.

  • Edit gradle.properties to strip -SNAPSHOT from profiler.version
  • Ensure everything is checked in: git commit -S -am "Prepare releasing 0.12.0"
  • Push your changes
  • Publish the version by using this Teamcity build. The build will upload the artifacts, add and push a tag and add the release to SDKMAN. If the version is a final version (it only contains numbers and dots), then it is announced and set as the default version on SDKMAN as well.
  • Increment the version in gradle.properties and append "-SNAPSHOT": echo "profiler.version=0.13.0-SNAPSHOT">gradle.properties
  • Commit the updated version number: git commit -S -am "Prepare next development version 0.13.0"
  • Push the version update
  • Update the release draft prepared by release-drafter, assign the tag you created and publish the release
  • The Publish to SDKman should trigger automatically after the publishing job finishes. Though it may fail, since the artifacts are not yet on Maven Central. The build will retry the SDKMan publishing after half an hour. If it still doesn't work, you can trigger the build manually.
  • All done!

Releasing Pre-release Versions

Releasing pre-release versions from the master branch is also supported. These versions are normally used for dogfooding in the gradle/gradle build. We use -alpha-<number> suffix for these versions, e.g. 0.21.0-alpha-1.

Process is the same as releasing the final versions, except that you should not publish the release draft. Also, the build will automatically detect a snapshot version if it contains snapshot or alpha and will skip publishing to SDKMan.

Latest version can be found in Maven Central.