From 04d3056dbd67b0df69aa5b81a00f46b62b3da29e Mon Sep 17 00:00:00 2001 From: Arnout Engelen Date: Fri, 15 Jan 2021 10:32:00 +0100 Subject: [PATCH] make sure to clean before publishing --- RELEASING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASING.md b/RELEASING.md index cb82f9f..3b4ccb8 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -15,4 +15,4 @@ It is often the case when this compiler plugin needs to be released for a newly * master, if no features or bug fixes were merged to master since the latest release * tag, if the master has unreleased 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. Alternatively you can `set version in ThisBuild := ...` in the command line. -1. Publish the release by running `SONATYPE_USERNAME=xxx SONATYPE_PASSWORD=xxx sbt ++2.12.13 publishSigned sonatypeBundleRelease` (with the appropriate credentials and scala version). You will need Sonatype OSS repository rights to publish under `com.typesafe` organisation. +1. Publish the release by running `SONATYPE_USERNAME=xxx SONATYPE_PASSWORD=xxx sbt clean ++2.12.13 publishSigned sonatypeBundleRelease` (with the appropriate credentials and scala version). You will need Sonatype OSS repository rights to publish under `com.typesafe` organisation.