Skip to content

Commit fe52f59

Browse files
authored
Merge pull request #786 from vsbogd/version-0.2.1
Update the version to 0.2.1
2 parents 27ce1cd + 009326a commit fe52f59

File tree

3 files changed

+14
-15
lines changed

3 files changed

+14
-15
lines changed

Cargo.toml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,11 @@ members = [
77
resolver = "2"
88

99
[workspace.package]
10-
version = "0.2.0"
10+
version = "0.2.1"
1111
edition = "2021"
1212

1313
[workspace.dependencies]
14-
hyperon = { path = "./lib", version = "0.2.0" }
14+
hyperon = { path = "./lib", version = "0.2.1" }
1515
regex = "1.11.0"
1616
log = "0.4.0"
1717
env_logger = "0.8.4"

docs/DEVELOPMENT.md

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -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
4545
release.
4646

4747
There 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
6867
artifacts.
6968

7069
After release job is finished one need to approve publishing artifacts to the

python/VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
'0.2.0'
1+
'0.2.1'

0 commit comments

Comments
 (0)