1.4 KiB
1.4 KiB
type, title, description, status
| type | title | description | status |
|---|---|---|---|
| User Story | US-001: Build and release the plugin | Give maintainers repeatable Purpur builds, automated verification, and versioned public Gitea releases. | in-progress |
US-001: Build and release the plugin
As a plugin maintainer, I want automated builds and releases modeled on Spigot Base so that tested, correctly versioned artifacts can be distributed consistently.
Acceptance criteria
- The Gradle project compiles against Purpur API
26.2.build.2618-stableusing a Java 25 toolchain. - Compiler lint warnings fail the build.
- Automated JUnit 5 tests run as part of the Gradle check lifecycle.
- Plugin metadata declares the entrypoint, player and admin commands, and permissions.
- Pushes and pull requests build and test the plugin in Gitea Actions.
- Pull requests validate conventional commit messages.
- CI stores a development JAR as a workflow artifact.
- Main-branch conventional commits drive semantic versioning.
- A successful release builds a versioned JAR and attaches it to the corresponding Gitea release.
- The project is published in the public
dmg/spigot-quest-boardGitea repository. - Build files, Gradle wrapper, workflows, and release behavior follow
../spigot-base/where applicable while using Spigot Quest Board names and identifiers.