docs: add info about manually package version setting to docs (#251)

Author: gorgeousvlad

README.md

@@ -306,6 +306,13 @@ In usual cases we use two types of commits:
 1. fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).
 2. feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).
 3. BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.
+4. To set release package version manually you need to add `Release-As: <version>` to your commit message e.g.
+
+```bash
+git commit -m 'chore: bump release
+
+Release-As: 1.2.3'
+```
 
 You can see all information [here](https://www.conventionalcommits.org/en/v1.0.0/).