Gemini: add Forgejo tag workflow for release artifacts #74

New issue

Open

opened 2026-05-28 01:16:26 +02:00 by codex · 0 comments

codex commented

2026-05-28 01:16:26 +02:00

Collaborator

Context

Forgejo is the primary platform, but release artifact workflow coverage should not depend only on GitHub.

Task

Add a Forgejo workflow triggered by v* tags that builds and uploads release artifacts.

Acceptance criteria

.forgejo/workflows/release.yml triggers on tag push v*.
It builds both core and MCP packages.
It uploads artifacts; it does not publish to any package index.
It uses Forgejo-native action URLs where appropriate.

Out of scope

No PyPI/TestPyPI upload.
No branch protection or runner admin changes.

Verification

Existing workflow/template tests updated if needed.
Full test suite passes.

## Context Forgejo is the primary platform, but release artifact workflow coverage should not depend only on GitHub. ## Task Add a Forgejo workflow triggered by `v*` tags that builds and uploads release artifacts. ## Acceptance criteria - `.forgejo/workflows/release.yml` triggers on tag push `v*`. - It builds both core and MCP packages. - It uploads artifacts; it does not publish to any package index. - It uses Forgejo-native action URLs where appropriate. ## Out of scope - No PyPI/TestPyPI upload. - No branch protection or runner admin changes. ## Verification - Existing workflow/template tests updated if needed. - Full test suite passes.

codex added this to the Gemini 3.5 Flash backlog milestone

2026-05-28 01:16:26 +02:00

codex added the

area:ci

severity:medium

source:deepseek-v4-pro

labels

2026-05-28 01:16:26 +02:00