From cee0378f8fe85d63157dd187be36bbc59b17414c Mon Sep 17 00:00:00 2001 From: Dylan Garvis Date: Sat, 1 Aug 2026 15:56:02 -0400 Subject: [PATCH] docs(design): verify bot release artifact --- design/log.md | 1 + design/us-016-automated-releases.md | 8 ++++---- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/design/log.md b/design/log.md index 55a7969..b1675d1 100644 --- a/design/log.md +++ b/design/log.md @@ -2,6 +2,7 @@ ## 2026-08-01 +* **Verify**: Confirmed the `v1.1.0` Discord bot image and matching web, migration, and Velocity artifacts. * **Extend**: Added a releasable Discord bot image and a dependency-free web health endpoint for Kubernetes deployment. * **Verify**: Confirmed the initial `v1.0.0` release, public Velocity JAR, and versioned and `latest` web and migration image manifests. * **Create**: Added Gitea CI and semantic-release pipelines for downloadable Velocity JARs and versioned web and migration images. diff --git a/design/us-016-automated-releases.md b/design/us-016-automated-releases.md index f599018..315b518 100644 --- a/design/us-016-automated-releases.md +++ b/design/us-016-automated-releases.md @@ -3,9 +3,9 @@ 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 +timestamp: 2026-08-01T19:55:10Z story_id: US-016 -status: implemented +status: verified --- # User Story @@ -21,7 +21,7 @@ As a platform operator, I want automated validation and semantic releases, so th - [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` 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. @@ -37,7 +37,7 @@ As a platform operator, I want automated validation and semantic releases, so th # 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. +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. Release `v1.1.0` also publishes resolvable versioned web, Discord bot, and migration manifests and a public Velocity JAR whose metadata reports `1.1.0`. Pull-request commitlint configuration is present; its conditional execution will be exercised by the first pull request. # Related Stories