From c7bcbecdf258084912be91aa41ab6eede3f45e67 Mon Sep 17 00:00:00 2001 From: Erich Blume Date: Sun, 15 Feb 2026 07:26:20 -0800 Subject: [PATCH] Review create-release-artifact-workflow doc: clarify and stamp Clarify that build-blumeops.yaml is only an example of the version bump pattern, not the full generic packages upload flow. Co-Authored-By: Claude Opus 4.6 --- docs/how-to/create-release-artifact-workflow.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/how-to/create-release-artifact-workflow.md b/docs/how-to/create-release-artifact-workflow.md index 829ff3e..80e0308 100644 --- a/docs/how-to/create-release-artifact-workflow.md +++ b/docs/how-to/create-release-artifact-workflow.md @@ -1,6 +1,7 @@ --- title: Create Release Artifact Workflow -modified: 2026-02-12 +modified: 2026-02-15 +last-reviewed: 2026-02-15 tags: - how-to - forgejo @@ -34,7 +35,7 @@ This is required because Forgejo's built-in `GITHUB_TOKEN` does not have permiss ## 2. Create the workflow -Create `.forgejo/workflows/-release.yaml` with `workflow_dispatch` and a version input. Use the semver bump pattern (see `cv-release.yaml` or `build-blumeops.yaml` for examples). +Create `.forgejo/workflows/-release.yaml` with `workflow_dispatch` and a version input. Use the semver bump pattern (see `cv-release.yaml` for the full upload flow, or `build-blumeops.yaml` for the version bump logic only — it uploads to Forgejo releases, not generic packages). The upload step uses `FORGE_TOKEN`: