28 lines
1.3 KiB
Markdown
28 lines
1.3 KiB
Markdown
---
|
|
type: User Story
|
|
title: "US-012: Build and release the plugin"
|
|
description: Give maintainers repeatable Spigot builds, automated verification, and versioned Gitea releases.
|
|
status: 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
|
|
|
|
- [x] The Gradle project compiles against Spigot API `26.2-R0.1-SNAPSHOT` using a Java 17 toolchain.
|
|
- [x] Compiler lint warnings fail the build.
|
|
- [x] Automated JUnit 5 tests run as part of the Gradle check lifecycle.
|
|
- [x] Pushes and pull requests build and test the plugin in Gitea Actions.
|
|
- [x] Pull requests validate conventional commit messages.
|
|
- [x] CI stores a development JAR as a workflow artifact.
|
|
- [x] Main-branch conventional commits drive semantic versioning.
|
|
- [x] A successful release builds a versioned JAR and attaches it to the corresponding Gitea release.
|
|
- [x] Build files, Gradle wrapper, workflows, and release behavior follow `../spigot-trigger-spawn/` where applicable while using Spigot Base names and identifiers.
|
|
|
|
## Related
|
|
|
|
- [US-011: Configure and persist progression](us-011-configure-and-persist-progression.md)
|
|
- [User-story catalog](index.md)
|