Triggered by a GitHub Release
Every time a GitHub release is published, a github action workflow is triggered, that does the following:
- build the mod
- publish to mod to Maven
- upload the mod to Modrinth
- upload the mod to CurseForge
It uses the release tag as the mod version and the release description as a changelog.
The mod_version property in the gradle.properties file is always set to 0.0.0-dev for these projects, as it will be overwritten by the CI when releasing.
Snapshot versions
If there is a draft release present in GitHub targeting a specific branch,
every pushed commit will trigger a build that will be published to Maven as a -SNAPSHOT version.
For example, a release draft targeting main/1.21.x with the tag 5.2.0 will build a mod jar with the version 5.2.0 and publish it as 5.2.0-SNAPSHOT.
This allows indev-builds to already be included in the dependencies of other mods that are using them as an API, before the version is completely finished and published to Modrinth/CurseForge.
