19 lines
1.6 KiB
Markdown
19 lines
1.6 KiB
Markdown
---
|
|
name: faerro-kb-release
|
|
description: Prepare and publish a versioned Faerro KB container image to the private Gitea registry.
|
|
---
|
|
|
|
# Faerro KB Release
|
|
|
|
Use this skill when asked to tag or publish a Faerro KB image. The release procedure is defined by `README.md` and `scripts/publish-image.sh`.
|
|
|
|
## Procedure
|
|
|
|
1. Check the worktree and identify the exact commit being released. Do not tag unrelated or unreviewed changes.
|
|
2. Use the release version explicitly supplied by the user. If no version was supplied and no approved version is established in the task, ask instead of guessing. Tags must be exact `MAJOR.MINOR.PATCH`, optionally prefixed with `v`.
|
|
3. Check that the chosen tag is unused and attach it to the intended commit.
|
|
4. Confirm Docker is available. For non-interactive authentication, put `GITEA_USERNAME` and a package-write `GITEA_TOKEN` in the ignored `.env` file. The script parses only these keys and sends the token through Docker's `--password-stdin`; never put credentials in tracked files, command-line arguments, or chat. Without these settings it relies on Docker's existing login credentials.
|
|
5. Run `./scripts/publish-image.sh` from the repository. It builds, logs in when `.env` credentials are set, and pushes both the versioned tag and `latest`.
|
|
6. Report the tagged commit, image tags, and actual build/push result. A successful local build is not a successful release if either registry push fails.
|
|
|
|
Do not force-move an existing tag, create or push Git tags to a remote unless requested, or claim publication succeeded without successful registry pushes. |