CI and version tags

Today, the workflow for publishing my mods changed once again - for the better! It also makes it easier to browse the correct source code for a given version.

Since I made a mistake on the publishing server back in early 2024, the Jenkins server used for building and uploading my mods hasn't been public since. During that time, there were reports of some mods being discovered as malware. Because of this, trust in a non-public build system was understandably low. In theory, I could have had a step in the build process that injected code into my mods without anyone knowing - and there's a good chance most people didn't even realize my mods were being built and uploaded automatically in the first place.

That changes today. I used some Claude Code tokens to put together a new workflow for publishing my mods via GitHub Actions. You can see its current state here in SimpleBackups. As of this writing, SimpleBackups is the only mod using it in full.

This workflow change will only apply to versions for Minecraft 26.1 and higher. Most of my mods still need to be migrated, and I'm working through that over the next few days.

As part of this switch, it's now much easier to find the source code for a specific mod version on GitHub - the workflow automatically creates a tag for each release, like here. Since a few mod versions are already public without tags, SimpleBackups is currently the only mod that's fully tagged. I'll be retro-tagging the 26.1+ versions of my other mods over the coming days as well.

As a user, this change won't affect you much day to day - but I hope it's a meaningful step toward building more trust in my mods, at least for new versions going forward. :)