46 lines
2.5 KiB
Markdown
46 lines
2.5 KiB
Markdown
---
|
|
type: User Story
|
|
title: Build and publish versioned releases
|
|
description: Gitea Actions validate every change and publish semantically versioned Velocity and container artifacts.
|
|
tags: [operations, ci, release, velocity, docker]
|
|
timestamp: 2026-08-01T19:46:09Z
|
|
story_id: US-016
|
|
status: implemented
|
|
---
|
|
|
|
# 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
|
|
|
|
- [x] Pushes and pull requests run OKF validation, linting, type checks, tests, the web build, and the Velocity build.
|
|
- [x] Pull requests validate conventional commit messages.
|
|
- [x] CI uploads the development Velocity JAR as a workflow artifact.
|
|
- [x] Main-branch conventional commits determine the next semantic version and create a `vMAJOR.MINOR.PATCH` tag.
|
|
- [x] A release build embeds the semantic version in the Velocity plugin and JAR filename.
|
|
- [x] A public Gitea release exposes the versioned Velocity JAR as a downloadable asset.
|
|
- [x] Releases publish versioned and `latest` web runtime images to the Gitea registry.
|
|
- [ ] Releases publish versioned and `latest` Discord bot images to the Gitea registry.
|
|
- [x] Releases publish versioned and `latest` migration images that run versioned Drizzle migrations.
|
|
- [x] Runtime containers use unprivileged users and exclude development source and secrets where practical.
|
|
- [x] Operators are told which repository secrets must be configured before the first push.
|
|
|
|
# Implementation
|
|
|
|
- [CI workflow](../.gitea/workflows/ci.yml)
|
|
- [Release workflow](../.gitea/workflows/release.yml)
|
|
- [Semantic Release configuration](../.releaserc)
|
|
- [Web and migration Docker targets](../Dockerfile)
|
|
- [Velocity Gradle build](../plugins/velocity/build.gradle.kts)
|
|
- [Release and deployment guide](../docs/releases.md)
|
|
|
|
# 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. Discord bot image publication is implemented for the next feature release. Pull-request commitlint configuration is present; its conditional execution will be exercised by the first pull request.
|
|
|
|
# Related Stories
|
|
|
|
- [Deploy and operate securely](us-015-platform-operations.md)
|
|
- [Velocity game admission](us-009-velocity-admission.md)
|