The
[semantic version]is bumped according to releases, new features, and breaking changes.The
developbranch uses the (semantic version) suffix-develop.
Note: this guide assumes that the your git torrust remote is like this:
git remote show torrust* remote torrust
Fetch URL: git@github.com:torrust/torrust-tracker.git
Push URL: git@github.com:torrust/torrust-tracker.git
...The develop branch should have the version [semantic version]-develop that is ready to be released.
git fetch --all
git push --force torrust develop:staging/maingit stash
git switch staging/main
git reset --hard torrust/staging/main
# change `[semantic version]-develop` to `[semantic version]`.
git add -A
git commit -m "release: version [semantic version]"
git push torrustPull request title format: "Release Version [semantic version]".
This pull request merges the new version into the main branch.
git fetch --all
git push torrust main:releases/v[semantic version]Check that the deployment is successful!
git switch releases/v[semantic version]
git tag --sign v[semantic version]
git push --tags torrustMake sure the deployment workflow was successfully executed and the new version for the following crates were published:
- torrust-tracker-contrib-bencode
- torrust-tracker-located-error
- torrust-tracker-primitives
- torrust-tracker-clock
- torrust-tracker-configuration
- torrust-tracker-torrent-repository
- torrust-tracker-test-helpers
- torrust-tracker
This is for those who wish to download the source code.
Merge release back into the develop branch.
git fetch --all
git push --force torrust main:staging/developgit stash
git switch staging/develop
git reset --hard torrust/staging/develop
# change `[semantic version]` to `(next)[semantic version]-develop`.
git add -A
git commit -m "develop: bump to version (next)[semantic version]-develop"
git push torrustPull request title format: "Version [semantic version] was Released".
This pull request merges the new release into the develop branch and bumps the version number.