From f624dfcf70c952b4f1fa88bd60fa3ecd80ef6c87 Mon Sep 17 00:00:00 2001 From: Brice Jaglin Date: Sat, 13 Jun 2020 13:49:55 +0200 Subject: [PATCH 1/2] fix code block --- CONTRIBUTING.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2a542a4b3..1c975ba5d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -108,6 +108,7 @@ curl -vvv -H "Authorization: Bearer $APPVEYOR_TOKEN" -XDELETE https://ci.appveyo First, kickstart a CI release to Sonatype by pushing a git tag that correspond to the desired commit +```sh git fetch && git log origin/master --pretty=oneline # choose the commit hash you want to tag COMMIT_HASH=14a069a3765739f5540129e8220104b17f233020 # change this variable VERSION=0.9.15 # change this variable From b119ea052a2e35fc7e452bd8cf94aa05a54b265a Mon Sep 17 00:00:00 2001 From: Brice Jaglin Date: Sat, 13 Jun 2020 13:53:16 +0200 Subject: [PATCH 2/2] release process: add note about website doc --- CONTRIBUTING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1c975ba5d..97d703f19 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -139,6 +139,10 @@ When scalafix and sbt-scalafix have both completed the release, edit the release draft in the GitHub web UI to point to the tag that you pushed and then click on "Publish release". +Confirm that the documentation is advertising the new versions +- https://scalacenter.github.io/scalafix/docs/users/installation.html#sbt +- https://scalacenter.github.io/scalafix/docs/users/installation.html#help + If everything went smoothly, congrats! Tweet about the release and comment with `@/all` on Gitter linking to the release notes.