fix: Use Gitea API for CI tag creation #12

cal · 2026-02-17T23:27:32Z

cal commented

2026-02-17 23:27:32 +00:00

Summary

Switch CI tag release step from git push origin main --tags to Gitea REST API (POST /api/v1/repos/{repo}/tags)
Removes VERSION file commit that failed against branch protection
Matches the fix already applied to Paper Dynasty's workflow

Test plan

Merge PR and verify Gitea Actions run completes successfully
Confirm CalVer tag is created via API (visible in repo tags)
Verify no branch protection errors in CI logs

🤖 Generated with Claude Code

## Summary - Switch CI tag release step from `git push origin main --tags` to Gitea REST API (`POST /api/v1/repos/{repo}/tags`) - Removes VERSION file commit that failed against branch protection - Matches the fix already applied to Paper Dynasty's workflow ## Test plan - [ ] Merge PR and verify Gitea Actions run completes successfully - [ ] Confirm CalVer tag is created via API (visible in repo tags) - [ ] Verify no branch protection errors in CI logs 🤖 Generated with [Claude Code](https://claude.com/claude-code)

cal added 1 commit 2026-02-17 23:27:34 +00:00

fix: use Gitea API for tag creation to avoid branch protection failures

Build Docker Image / build (pull_request) Successful in 1m10s

Details

5745a2334a

The git push approach fails on protected main branches. Switch to the
Gitea REST API (POST /repos/{repo}/tags) matching the fix already
applied to Paper Dynasty's workflow.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

cal merged commit e0d86785a6 into main

2026-02-17 23:28:53 +00:00

cal deleted branch fix/ci-tag-release-api

2026-02-17 23:28:53 +00:00

cal referenced this issue from a commit

2026-02-17 23:28:55 +00:00

Merge pull request 'fix: Use Gitea API for CI tag creation' (#12) from fix/ci-tag-release-api into main

Sign in to join this conversation.

No reviewers