Skip to content

Latest commit

 

History

History
46 lines (40 loc) · 1.84 KB

RELEASING.md

File metadata and controls

46 lines (40 loc) · 1.84 KB

Production Releases

  1. Checkout origin/main.
  2. Update the CHANGELOG.md file with the changes of this release.
  3. Update the version in gradle.properties and remove the -SNAPSHOT suffix.
  4. Commit the changes and create a tag: 
    git commit -am "Releasing v0.1.0."
git tag v1.0.0
  5. Push the artifacts to Maven Central and the Gradle Plugin Portal. 
    ./gradlew clean uploadArchives --no-daemon --no-parallel --no-build-cache && cd gradle-plugin && ./gradlew clean uploadArchives publishPlugins --no-daemon --no-parallel --no-build-cache && cd ..
  6. Close and release the staging repository at Sonatype.
  7. Update the version in gradle.properties and add the -SNAPSHOT suffix.
  8. Commit the change: 
    git commit -am "Prepare next development version."
  9. Push git changes: 
    git push && git push --tags
  10. Create the release on GitHub:
    1. Go to the Releases page for the GitHub project.
    2. Click "Draft a new release".
    3. Enter the tag name you just pushed.
    4. Title the release with the same name as the tag.
    5. Copy & paste the changelog entry for this release into the description.
    6. If this is a pre-release version, check the pre-release box.
    7. Hit "Publish release".

Installing in Maven Local

./gradlew clean publishToMavenLocal --no-build-cache && cd gradle-plugin && ./gradlew clean publishToMavenLocal --no-build-cache && cd ..

Notes

Snapshot Releases

Snapshot releases are similar to production releases. Only make sure that the version contains the -SNAPSHOT suffix. Closing and releasing the staging repository on Sonatype is not necessary for snapshot releases. You can verify the release here.