Merge pull request #542 from ably/add-release-process-codegen

docs: add unasync codegen step to release process

Author: owenpearson

CONTRIBUTING.md

@@ -38,9 +38,10 @@ The release process must include the following steps:
 5. Commit this change: `git add CHANGELOG.md && git commit -m "Update change log."`
 6. Push the release branch to GitHub
 7. Create a release PR (ensure you include an SDK Team Engineering Lead and the SDK Team Product Manager as reviewers) and gain approvals for it, then merge that to `main`
-8. From the `main` branch, run `poetry build && poetry publish` to build and upload this new package to PyPi
-9. Create a tag named like `v2.0.1` and push it to GitHub - e.g. `git tag v2.0.1 && git push origin v2.0.1`
-10. Create the release on GitHub including populating the release notes
+8. Build the synchronous REST client by running `poetry run unasync`
+9. From the `main` branch, run `poetry build && poetry publish` to build and upload this new package to PyPi
+10. Create a tag named like `v2.0.1` and push it to GitHub - e.g. `git tag v2.0.1 && git push origin v2.0.1`
+11. Create the release on GitHub including populating the release notes
 
 We tend to use [github_changelog_generator](https://github.com/skywinder/Github-Changelog-Generator) to collate the information required for a change log update.
 Your mileage may vary, but it seems the most reliable method to invoke the generator is something like: