Minecraft CI / Release Skill

Routing Boundaries

• Use when: the task is CI/CD pipelines, artifact publishing, versioning, or release governance.
• Do not use when: the task is gameplay or plugin implementation (minecraft-modding, minecraft-plugin-dev, or minecraft-datapack).
• Do not use when: the task is server runtime operations or infrastructure tuning (minecraft-server-admin).

Release Shape

Keep each repository's existing release destinations and approval policy. A tag can build an artifact and create a GitHub Release without publishing to Modrinth or CurseForge. Add a publisher only when the project already uses it or the user asks for it. Never add tokens to committed files.

For the current Minecraft 26.x lane, use Java 25 and state that in workflow labels and examples. Legacy Minecraft 1.21.x projects stay on Java 21; retain their own loader and Gradle conventions instead of mechanically changing their version.