RELEASING.md

Releasing

Create a new issue from the Release Train Issue Template:

$ sh ./scripts/create-release-issue.sh 0.x.y

Gradle plugin release details

The Gradle plugin goes directly to the Gradle Plugin Portal. An encrypted gradle.properties that includes a publishing key and password is checked in under gradle.properties.enc and is decrypted by a private key known only to travis.

Releasing only updated docs

It is possible to release a revised documentation to the already existing release.

1. Create a new branch from a release tag. If a revised documentation is for the v0.3 release, then the name of the new branch should be docs/v0.3.
2. Add and commit version.sbt file that pins the version to the one, that is being revised. Also set isSnapshot to false for the stable documentation links. For example:

   ThisBuild / version := "0.6.1"
   ThisBuild / isSnapshot := false

3. Make all of the required changes to the documentation.
4. Build documentation locally with CI settings:

   env CI=true sbt akka-grpc-docs/previewSite

5. If the generated documentation looks good, send it to Gustav:

   env CI=true sbt akka-grpc-docs/publishRsync

6. Do not forget to push the new branch back to GitHub.