New artifacts use build/libs/purpur-tyrant-<version>.jar. Gitea CI checks pushes/pull requests; approved conventional commits on main drive versioned releases. Distribution tests inspect the actual JAR, version, Java 25 bytecode, retained runtime identity and workflow names.

The full verification command compiles against Purpur API 26.3.build.2651-stable, downloads build 2651 from the Purpur API, verifies SHA-256 0677c1febecfbc2e5b0a7f76abd647b70a1f38d3cbdf3dd6a82e401b4262a598, and starts a clean loopback-only Purpur server. The native lifecycle check loads, enables, commands, and disables the packaged plugin while proving persisted role/game state and a captured-entity snapshot survive the cycle. It uses generated build-local server state, not the untracked Compose environment, and is automated compatibility evidence rather than a live-player test.

Migration compatibility

The repository and checkout are now purpur-tyrant, previously spigot-tyrant. Runtime identity remains SpigotTyrant, including plugins/SpigotTyrant/, Java entrypoints/packages, command/permission names and persistent keys for roles, captured mobs and legacy items. The migration changes the build/distribution target, not gameplay or persisted schemas. New releases no longer support Java 17.

Replace the old plugin JAR rather than installing both distributions. Old tags/assets remain available; both the origin GitOps v1.24.0 and separately prepared local v1.25.0 URLs were verified to redirect and download identical bytes after the repository rename. No deployment or GitOps push is implied by publication.

Unrelated local testing files are preserved; their commands may still reference the historical artifact names.

See the canonical project, stories, and development cycle.