diff --git a/design/log.md b/design/log.md index 4621a39..df7770d 100644 --- a/design/log.md +++ b/design/log.md @@ -19,6 +19,12 @@ description: Chronological record of material decisions affecting the Spigot Inv - The Sorting Stick uses a vertical recipe in the crafting grid's center column: a Chest or Barrel above Redstone Dust, with a Stick at the bottom. - Either storage-block variant produces one Sorting Stick. +## 2026-09-04 — Build and release foundation completed + +- Added the Java 25 Gradle build, Purpur API dependency, strict compiler linting, JUnit 5 lifecycle, plugin metadata, and initial plugin entry point. +- Added Gitea CI, conventional-commit validation for pull requests, development artifacts, semantic releases, and release-asset upload. +- Verified `./gradlew clean check jar`, successful main and tag CI runs, and release `v1.0.0` with `spigot-inventory-helper-1.0.0.jar` attached. + ## 2026-09-04 — Implementation started - Approved implementation begins with the tested Gradle and Purpur foundation, followed by the Sorting Stick, inventory sorting, and automatic tool replacement. diff --git a/design/user-stories/us-001-build-and-release-plugin.md b/design/user-stories/us-001-build-and-release-plugin.md index a7a715d..5c541be 100644 --- a/design/user-stories/us-001-build-and-release-plugin.md +++ b/design/user-stories/us-001-build-and-release-plugin.md @@ -2,7 +2,7 @@ type: User Story title: "US-001: Build and release the plugin" description: Give maintainers repeatable Purpur builds, automated verification, and versioned Gitea releases. -status: in-progress +status: done --- # US-001: Build and release the plugin @@ -11,15 +11,15 @@ As a **plugin maintainer**, I want repeatable builds and automated releases so t ## Acceptance criteria -- [ ] The Gradle project compiles against Purpur API `26.2.build.2618-stable` using a Java 25 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-base/` where applicable while using Spigot Inventory Helper names and identifiers. +- [x] The Gradle project compiles against Purpur API `26.2.build.2618-stable` using a Java 25 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-base/` where applicable while using Spigot Inventory Helper names and identifiers. ## Related