Skip to content

Latest commit

 

History

History
19 lines (15 loc) · 1.53 KB

RELEASING.md

File metadata and controls

19 lines (15 loc) · 1.53 KB
Raw

Creating a regular release

  1. Create a new release with:
  • the next tag version (e.g. v0.11)
  • title and release description including notable changes
  • link to the milestone showing an overview of closed issues for this release
  1. Checkout the newly created tag and publish the release by running sbt publishSigned. You will have to have Sonatype OSS repository rights to publish under com.typesafe organisation.
  2. Login to Sonatype to close and release the repository.

Back-releasing for a new Scala version

It is often the case when this compiler plugin needs to be released for a newly released Scala version. For this the process is the following:

  1. Checkout the version that is to be back-released, which would be
  • master, if no features or bug fixes were merged to master since the latest release
  • tag, if the master has unlrealeased features or bug fixes. In this case you will need to cherry pick the commit that adds support for the new Scala version.
  1. Create a file version.sbt containing version in ThisBuild := "0.11" which sets the version to be back-released. This will override the automatic version derivation from the git history.
  2. Publish the release by running sbt publishSigned. You will have to have Sonatype OSS repository rights to publish under com.typesafe organisation.
  3. Login to Sonatype to close and release the repository.