Update release documentation

Dazu-io · Mar 30, 2020 · 1a045bb · 1a045bb
1 parent 7a05acd
commit 1a045bb
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/README.md b/README.md
@@ -154,7 +154,10 @@ Releasing a new version is quite simple, as the packages are build and distribut
 
 *Release steps*:
 1. Make sure all dependencies are up to date (**especially Rasa SDK**)
+  - For Rasa SDK that means first creating a [new Rasa SDK release](https://github.com/RasaHQ/rasa-sdk#steps-to-release-a-new-version) (make sure the version numbers between the new Rasa and Rasa SDK releases match)
+  - Once the tag with the new Rasa SDK release is pushed and the package appears on [PyPI](https://pypi.org/project/rasa-sdk/), the dependency in the rasa repository can be resolved.
 2. Switch to the branch you want to cut the release from (`master` in case of a major / minor, the current feature branch for patch releases) 
+  - Update the `rasa-sdk` entry in `pyproject.toml` with the new release version and run `poetry update`. This creates a new `poetry.lock` file with all dependencies resolved.
 3. Run `make release`
 4. Create a PR against master or the release branch (e.g. `1.2.x`)
 5. Once your PR is merged, tag a new release (this SHOULD always happen on master or release branches), e.g. using