eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Review create-release-artifact-workflow doc: clarify and stamp

Browse source 
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 <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-02-15 07:26:20 -08:00
commit c7bcbecdf2
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/how-to/create-release-artifact-workflow.md
View file

@ -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/<name>-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/<name>-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`: