@@ -20,9 +20,9 @@ Before making changes, create a new branch (if not already on one):
2020
2121``` console
2222$ git fetch
23- $ git switch -c release/v0.0.18 origin/main
24- branch 'release/v0.0.18 ' set up to track 'origin/main'.
25- Switched to a new branch 'release/v0.0.18 '
23+ $ git switch -c release/v0.0.19 origin/main
24+ branch 'release/v0.0.19 ' set up to track 'origin/main'.
25+ Switched to a new branch 'release/v0.0.19 '
2626```
2727
2828If already on a new branch, ensure ` HEAD ` is the same as the remote's ` main ` .
@@ -32,7 +32,7 @@ from `git cliff` follow the repository history in the correct linear order.
3232On rebase, quickly redo the generative steps with ` just ` :
3333
3434``` shell
35- just release-step-update-rust-dependencies && just release-step-refresh-changelog v0.0.18
35+ just release-step-update-rust-dependencies && just release-step-refresh-changelog v0.0.19
3636```
3737
3838## Dependency upgrades
@@ -81,7 +81,7 @@ table to define the version for all subpackages.
8181
8282``` toml
8383[workspace .package ]
84- version = " 0.0.18 "
84+ version = " 0.0.19 "
8585```
8686
8787Each package inherits this version by setting ` package.version.workspace = true ` .
@@ -105,7 +105,7 @@ table. E.g.,:
105105``` toml
106106[workspace .dependencies ]
107107# workspace local packages
108- firewood = { path = " firewood" , version = " 0.0.18 " }
108+ firewood = { path = " firewood" , version = " 0.0.19 " }
109109```
110110
111111This allows packages within the workspace to inherit the dependency,
@@ -136,10 +136,10 @@ is correct and reflects the new package versions.
136136To build the changelog, see git-cliff.org. Short version:
137137
138138``` sh
139- just release-step-refresh-changelog v0.0.18
139+ just release-step-refresh-changelog v0.0.19
140140```
141141
142- where ` v0.0.18 ` is the newest tag. This is a required paramter to ensure the
142+ where ` v0.0.19 ` is the newest tag. This is a required paramter to ensure the
143143changelog has the correct headers.
144144
145145## Commit
@@ -169,11 +169,11 @@ To trigger a release, push a tag to the main branch matching the new version,
169169# be sure to switch back to the main branch before tagging
170170git checkout main
171171git pull --prune
172- git tag -s -a v0.0.18 -m ' Release v0.0.18 '
173- git push origin v0.0.18
172+ git tag -s -a v0.0.19 -m ' Release v0.0.19 '
173+ git push origin v0.0.19
174174```
175175
176- for ` v0.0.18 ` for the merged version change. The CI will automatically publish a
176+ for ` v0.0.19 ` for the merged version change. The CI will automatically publish a
177177draft release which consists of release notes and changes (see
178178[ .github/workflows/release.yaml] ( .github/workflows/release.yaml ) ).
179179
0 commit comments