@@ -41,7 +41,7 @@ documentation](https://cibuildwheel.pypa.io/en/stable/) for details.
4141
4242## How to update the version
4343
44- Usually it is needed after releasing the artifacts or before making a test
44+ Usually it is needed before releasing the artifacts or before making a test
4545release.
4646
4747There are three locations to update:
@@ -54,17 +54,16 @@ All three locations should contain the same version.
5454
5555## How to release binaries
5656
57- Use [ Create a new release
58- link] ( https://github.com/trueagi-io/hyperon-experimental/releases/new ) on the
59- main page of the GitHub repo. Press ` Choose a tag ` control and type new tag
60- which should be in form of ` v<next-version> ` (for example if next version is
61- ` 0.1.7 ` then tag is ` v0.1.7 ` ). Next version should be identical to versions
62- which are written in locations mentioned in [ How to update the
63- version] ( #how-to-update-the-version ) instruction. After typing the tag press
64- ` Create new tag on publish ` . Now press ` Generate release notes ` button. It will
65- automatically fill the ` Release title ` and ` Release description ` fields. Tick
66- ` Set as a pre-release ` checkbox if needed and press ` Publish release ` button.
67- Now you have published new GitHub release and triggered a job to build release
57+ Update the version [ How to update the version] ( #how-to-update-the-version ) in
58+ the main branch of the repository, raise PR and merge it. Use [ Create a new
59+ release link] ( https://github.com/trueagi-io/hyperon-experimental/releases/new )
60+ on the main page of the GitHub repo. Press ` Choose a tag ` control and type new
61+ tag which should be in form of ` v<version> ` (for example if version is
62+ ` 0.1.7 ` then tag is ` v0.1.7 ` ). After typing the tag press `Create new tag
63+ on publish` . Now press ` Generate release notes` button. It will automatically
64+ fill the ` Release title ` and ` Release description ` fields. Tick `Set as a
65+ pre-release` checkbox if needed and press ` Publish release` button. Now you
66+ have published new GitHub release and triggered a job to build release
6867artifacts.
6968
7069After release job is finished one need to approve publishing artifacts to the
0 commit comments