minecraft-ci-release

Automate Minecraft mod publishing by enabling GitHub Actions workflows that handle Gradle builds and deploy artifacts directly to Modrinth and CurseForge. This reduces manual steps and human error across multi-platform release processes.

Yes, you can build a CI matrix for NeoForge and Fabric to test Minecraft mods and plugins across multiple versions. This ensures broad compatibility and validates builds before any automated release is triggered.

The best way to trigger a Minecraft mod release is by tagging a release with a semantic version like vX.Y.Z. This activates the automated workflow, generating GitHub Releases with artifacts and integrated changelogs.

Yes, this Minecraft CI workflow supports Paper plugin development by automating shadow JAR builds. It coordinates multi-platform releases alongside NeoForge and Fabric builds within the same pipeline.

Gradle dependencies in automated Minecraft release pipelines are managed using Dependabot updates and semantic versioning conventions. This maintains build stability and automates changelog generation for each release cycle.

Node.js is required to run the scripts that define and execute these automated Minecraft mod release workflows. It processes the YAML workflow definitions and manages Gradle-based publishing tasks securely.