2.3 KiB
2.3 KiB
type, title, description, tags, timestamp, story_id, status
| type | title | description | tags | timestamp | story_id | status | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| User Story | Build and publish versioned releases | Gitea Actions validate every change and publish semantically versioned Velocity and container artifacts. |
|
2026-08-01T19:18:42Z | US-016 | verified |
User Story
As a platform operator, I want automated validation and semantic releases, so that deployable web, migration, and Velocity artifacts are reproducible and downloadable.
Acceptance Criteria
- Pushes and pull requests run OKF validation, linting, type checks, tests, the web build, and the Velocity build.
- Pull requests validate conventional commit messages.
- CI uploads the development Velocity JAR as a workflow artifact.
- Main-branch conventional commits determine the next semantic version and create a
vMAJOR.MINOR.PATCHtag. - A release build embeds the semantic version in the Velocity plugin and JAR filename.
- A public Gitea release exposes the versioned Velocity JAR as a downloadable asset.
- Releases publish versioned and
latestweb runtime images to the Gitea registry. - Releases publish versioned and
latestmigration images that run versioned Drizzle migrations. - Runtime containers use unprivileged users and exclude development source and secrets where practical.
- Operators are told which repository secrets must be configured before the first push.
Implementation
- CI workflow
- Release workflow
- Semantic Release configuration
- Web and migration Docker targets
- Velocity Gradle build
- Release and deployment guide
Validation
Local OKF, lint, typecheck, test, Next.js build, and versioned Velocity JAR checks pass. Initial Gitea CI and release runs succeeded. Release v1.0.0 provides a publicly downloadable JAR whose Velocity metadata reports 1.0.0. Registry manifests were resolved for versioned and latest web and migration images. Pull-request commitlint configuration is present; its conditional execution will be exercised by the first pull request.