@@ -16,23 +16,27 @@ Optionally, if you want to have a GitHub Pull-Request automatically created, you
1616
1717## Usage
1818
19- Go to the folder containing a Cargo workspace or crate and run:
19+ To make a release pull-request, go to the folder containing a Cargo workspace or crate and run:
2020
21- release.sh [<next-devel-level>] [false]
21+ release.sh release
2222
23- where ` next-devel-level ` is the version level to be increased * after * the release is done. This ca be ` major ` , ` minor ` or ` patch ` .
23+ To bump the version and create pull-request:
2424
25- This pushes two commits in a newly created release branch. When merging, __ do not squash them__ .
25+ release.sh [<next-devel-level>]
26+
27+ where ` next-devel-level ` is the version level to be bumped. This ca be ` major ` , ` minor ` or ` patch ` .
28+
29+ This pushes two commits in a newly created release branch.
2630
2731Examples:
2832
29- # Perform release and raise the minor version afterwards
30- $ release.sh
33+ # Perform release
34+ $ release.sh release
3135
32- # Perform a release but do not push anything to origin
36+ # Bump the minor version but do not push anything to origin
3337 $ release.sh minor false
3438
35- # Perform a release and raise the major version for the next development version
39+ # Bump the major version, push and make a pull-request
3640 $ release.sh major
3741
3842## Description
@@ -41,13 +45,15 @@ The release process performs the following steps:
41450 . Create a release branch from ` main ` .
42461 . Update the release version in the cargo workspace by dropping the "-nightly" token.
43472 . Update ` Cargo.lock ` with the new version.
44- 3 . Commit and tag the release.
45- 4 . Set the version to the next development version by increasing the 'minor' (by default) part and adding the '-nightly' prerelease token.
46- 5 . Update ` Cargo.lock ` with the new version.
47- 6 . Commit the next release.
48- 7 . Push the two commits. This is skipped if the second argument was ` false ` .
49- 8 . __ Optional__ : if the GitHub cli is installed, a PR is created. This is also skipped if the second argument was ` false ` .
50-
51- ## Future development
48+ 3 . Regenerate Helm chart and manifests.
49+ 4 . Update the CHANGELOG.md entry of this release
50+ 5 . Commit, tag and push the changes.
51+ 6 . __ Optional__ : if the GitHub cli is installed, a PR is created.
5252
53- Automatically update the change log and readme files.
53+ Raising the next development version includes the following steps:
54+ 0 . Create a release branch from ` main ` .
55+ 1 . Set the version to the next development version by increasing the 'next-devel-level' (by default) part and adding the '-nightly' prerelease token.
56+ 2 . Update ` Cargo.lock ` with the new version.
57+ 3 . Regenerate Helm chart and manifests.
58+ 4 . Commit and push
59+ 5 . __ Optional__ : if the GitHub cli is installed, a PR is created.
0 commit comments