@@ -176,14 +176,20 @@ make dev
176
176
177
177
to sync your installed packages with the updated versions pinned in ` requirements/development.txt ` .
178
178
179
- ## Versioning
180
-
181
- This project uses [ SemVer] for versioning with no additional suffix after the version number. When
182
- it is time for a new release, run the command ` make version_{type} ` where ` {type} ` should be
183
- replaced with one of ` major ` , ` minor ` , ` patch ` depending on the type of changes in the release.
184
-
185
- The command will update the version in ` pyproject.toml ` and move the changes from the "Unreleased"
186
- section of the changelog to a versioned section and create a new "Unreleased" section for future
187
- improvements.
179
+ ## How to release a new version to Pypi
180
+
181
+ 1 . On your branch, run the appropriate command, depending on which kind of release it is:
182
+ - either ` make version_major `
183
+ - or ` make version_minor `
184
+ - or ` make version_patch ` .
185
+ 2 . Review the commit that has just been made (note it will have updated the version based on [ SemVer] ).
186
+ 3 . Push the commit, get it reviewed and merge it to ` main ` .
187
+ 4 . Once it's merged, tag the merge commit and push tags:
188
+ - ` git checkout main && git pull `
189
+ - ` git tag v0.0.0 `
190
+ - ` git push --tags `
191
+ 5 . Keep an eye on the [ release workflow] which should have started. Check that it completes, and the latest version has
192
+ made its way onto [ Pypi] ( https://pypi.org/project/rustfluent/ ) .
188
193
189
194
[ semver ] : https://semver.org/
195
+ [ release workflow ] : https://github.com/kraken-tech/python-rustfluent/actions/workflows/release.yml
0 commit comments