-
v0.3.2: CI Publish Pipeline
Pre-releaseAll checks were successfulCI / validate-release-pr (push) Has been skippedPublish / tag (push) Successful in 10sPublish / promote-release (push) Successful in 1sCI / validate-branch (push) Has been skippedPublish / detect-release (push) Successful in 6sCI / test (push) Successful in 1m38sCI / security (push) Successful in 1m57sCI / build (push) Successful in 2m0sCI / lint (push) Successful in 2m47sreleased this
2026-02-17 23:07:02 +00:00 | 212 commits to main since this releaseSummary
Adds automated release publishing to CI, removing manual tag creation and release promotion from the release workflow.
Changes
Publish Workflow (
.forgejo/workflows/publish.yml)- detect-release — compares
manifest.jsonversion between HEAD and HEAD~1 on push to main - tag — verifies no existing tag, checks draft release exists, creates and pushes
v{version}tag - promote-release — promotes matching draft Forgejo release to published (or creates one if missing)
Release Validation Gates (
ci.yaml)- validate-branch — only
release/*branches can target main via PR - validate-release-pr — PR title must match
Release v{version}from manifest.json; draft release must exist
Version Source of Truth
- Added
manifest.jsonwithnameandversionfields - Replaces manual git tagging in Phase 2 of the release workflow
Work Packages
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
- detect-release — compares