Update dev docs with cargo publish cmds (#837)

* update readme

* update dev doc

* add link to release generation

* fix spelling

Author: haerdib

docs/README.md

@@ -3,13 +3,21 @@
 ## TODO List for a new Release
 If a new release is released, the following tasks need to be done:
 1. Update the .toml versions in accordance with the [Semantic Versioning](../README.md#version-numbers) section.
-2. Add a new tag to the desired commit, see the [Tag generation](#tag-generation) section.
-3. Update and release the new release.
-4. Create a new branch and change all github deps to crates.io deps. See https://github.com/scs/substrate-api-client/issues/528 for an example update. The [psvm](https://crates.io/crates/psvm) tool can be useful for updating the polkadot dependencies.
-5. Publish to crates.io, see https://doc.rust-lang.org/cargo/reference/publishing.html for more info.
-
-
-## Automatic Release generation
+1. Create a new branch and change all github deps to crates.io deps. See https://github.com/scs/substrate-api-client/issues/812 for an example update. The [psvm](https://crates.io/crates/psvm) tool can be useful for updating the polkadot dependencies.
+1. Add a new tag to the desired commit, see the [Tag generation](#tag-generation) section.
+1. Update and release the new release (see [Automatic Release Generation](#automatic-release-generation)).
+1. Publish to crates.io (see https://doc.rust-lang.org/cargo/reference/publishing.html for more info):
+	```shell
+	cargo login <Crates.io Token>
+	# Only run the next steps if CI has run successfully.
+	cargo publish -p ac-primitives
+	cargo publish -p ac-keystore
+	cargo publish -p ac-node-api
+	cargo publish -p ac-compose-macros
+	cargo publish
+	```
+
+## Automatic Release Generation
 
 A new draft release gets generated upon a new tag with a name matching `v[0-9]+.[0-9]+.[0-9]+*` (E.g. v1.2.3 and v1.2.3-rc1)
 See the workflow: https://github.com/scs/substrate-api-client/blob/master/.github/workflows/draft-release.yml