1.3 KiB
1.3 KiB
type, title, description, status
| type | title | description | status |
|---|---|---|---|
| User Story | US-012: Build and release the plugin | Give maintainers repeatable Spigot builds, automated verification, and versioned Gitea releases. | done |
US-012: Build and release the plugin
As a plugin maintainer, I want automated builds and releases modeled on Trigger Spawn so that tested, correctly versioned artifacts can be distributed consistently.
Acceptance criteria
- The Gradle project compiles against Spigot API
26.2-R0.1-SNAPSHOTusing a Java 17 toolchain. - Compiler lint warnings fail the build.
- Automated JUnit 5 tests run as part of the Gradle check lifecycle.
- 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.
- Build files, Gradle wrapper, workflows, and release behavior follow
../spigot-trigger-spawn/where applicable while using Spigot Base names and identifiers.