Releasing

Releasing

Releases come from the “Release” workflow on GitHub, run by hand or by the weekly autopilot.

1. Write the notes. Add a “## X.Y.Z” section to CHANGELOG.md and push. Patch for fixes, minor for features, major for breaking changes.
2. Run the workflow:

   gh workflow run release.yml -R allay-ai/minecraft -f version=X.Y.Z

   Its changelog field overrides the section, and one of the two must be there.
3. Watch it with gh run watch.

The workflow builds with -PreleaseVersion, runs the tests, tags vX.Y.Z, and attaches two jars to a GitHub release: allay-spigot-X.Y.Z.jar and allay-spigot.jar, so releases/latest/download/allay-spigot.jar always fetches the newest one. Its deploy job then ships the release to Moonlands.

Never delete or re-tag a published release.

Modrinth and Hangar

The build is ready for both stores, where the project is called “Allay AI”. The projects don't exist yet. Once they do, -f modrinth=true -f hangar=true also publishes there, and the Modrinth upload syncs MODRINTH.md as the project's description. The tokens are the MODRINTH_TOKEN and HANGAR_TOKEN secrets.

Next: Development