Set up Gitea Actions: build, test, and publish delegate-ai-mcp to this repo's package registry #7
Assignees
haylan (Arthur Erlich)
Clear assignees
haylan (Arthur Erlich)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: haylan/delegate-ai-mcp#7
Reference in New Issue
Block a user
Part of TypeScript project conventions for delegate-ai-mcp
Blocked by Build & typecheck strategy for delegate-ai-mcp
Question / task
Graduated from the map's 'CI' and 'npm-publish' fog once Build & typecheck strategy for delegate-ai-mcp decided to build now (tsc→build/) specifically so this repo's package can be published to its own Gitea package registry sooner rather than later.
Task: provision a Gitea Actions workflow that runs on push (build via tsc, run test/qwen-delegate.test.ts via node --test) and publishes to this Gitea instance's npm-compatible package registry (git.arthurerlich.de) on tag/release. tea has no package-registry command for this — needs a workflow YAML plus a registry auth token (Gitea Actions has a built-in GITEA_TOKEN, but publishing to the package registry may need a PAT with package:write scope — confirm which). AFK where possible (writing the workflow file); HITL for anything needing a human to click through Gitea's UI (enabling Actions on the repo if not already on, creating/scoping a token, first real publish to confirm it lands in the registry).
Closed as out of scope: this ticket depended on ticket #3's 'build now' decision, which was reverted. User wants to keep writing TypeScript directly with no build process, so there's nothing to build/test/publish via Gitea Actions right now. Deferred back to the map's fog, not resolved.