This file describes how to make the various kinds of releases.
- Verify that all Github Action workflows succeed on master.
- Update version in swagger.json and CITATION.cff.
- Ensure CHANGELOG is up-to-date (e.g. version and release date is set).
- Commit changes.
- Build software and push to maven repository:
rm -f release.properties
mvn clean release:prepare -Prelease-prepareAn additional call of mvn release:perform is not necessary! A GitHub Action workflow performs this
tasks automatically.
- Wait for the GitHub Action to deploy new version to Maven Central (Deploy workflow).
- Deploy to our public super peers (this is done with Ansible).
- Create Release on GitHub:
- Go to https://github.com/drasyl/drasyl/tags.
- Click
Create releasefor tagv1.2.0. - Title:
v1.2.0 - Description:
[CHANGELOG.md](https://github.com/drasyl-overlay/drasyl/blob/v1.2/CHANGELOG.md)
The assets below contain the drasyl command-line tool and shared native library. To learn how to integrate the overlay network into your application, please read our [documentation](https://docs.drasyl.org/getting-started/).- Wait for GitHub Action to complete Release workflow.
- Update back to next SNAPSHOT version in swagger.json.
- Create/update version branch (e.g.,
v1.2if you releasev1.2.0) and push.
The drasyl docker image should autobuild on via GitLab CI. If it doesn't or needs to be updated then rebuild like this.
mvn package
docker build -t drasyl/drasyl:1.2.0 -t drasyl/drasyl:1.2 -t drasyl/drasyl:1 -t drasyl/drasyl:latest .
docker push drasyl/drasyl:1.2.0
docker push drasyl/drasyl:1.2
docker push drasyl/drasyl:1
docker push drasyl/drasyl:latest