Hiddenden/AegisGitea-MCP
3
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

ci: reuse existing REGISTRY_TOKEN secret for package publish #60

Merged
Latte merged 1 commits from feat/publish-reuse-registry-token into dev 2026-06-27 12:49:18 +00:00
Conversation 0 Commits 1 Files Changed 2
+19 -16
Latte commented 2026-06-27 12:47:31 +00:00
Owner
Copy Link
Copy Source

Summary

Re-applies the publish-workflow credential fix that landed after PR #59 was merged and therefore never reached dev.

.gitea/workflows/publish.yml now reuses the existing REGISTRY_TOKEN package secret (the same write:package PAT docker.yml uses) instead of requiring new GITEA_PACKAGE_* secrets. It authenticates uv publish as GITHUB_ACTOR with the token as password, and fails loudly if the secret is absent. docs/packaging.md updated to match.

No code changes — CI workflow + docs only. The v*-tag publish job is now ready to run with no new secret setup.

Notes

  • Targets dev per the flow HEAD → feature → dev → main.
  • Single commit, cherry-picked from the merged branch (original c551b3c).

🤖 Generated with Claude Code

## Summary Re-applies the publish-workflow credential fix that landed after PR #59 was merged and therefore never reached `dev`. `.gitea/workflows/publish.yml` now reuses the **existing** `REGISTRY_TOKEN` package secret (the same `write:package` PAT `docker.yml` uses) instead of requiring new `GITEA_PACKAGE_*` secrets. It authenticates `uv publish` as `GITHUB_ACTOR` with the token as password, and fails loudly if the secret is absent. `docs/packaging.md` updated to match. No code changes — CI workflow + docs only. The `v*`-tag publish job is now ready to run with no new secret setup. ## Notes - Targets `dev` per the flow `HEAD → feature → dev → main`. - Single commit, cherry-picked from the merged branch (original `c551b3c`). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Latte added 1 commit 2026-06-27 12:47:32 +00:00
ci: reuse existing REGISTRY_TOKEN secret for package publish
docker / test (pull_request) Successful in 34s
Details
test / test (pull_request) Successful in 43s
Details
docker / docker (pull_request) Successful in 39s
Details
docker / test (push) Successful in 34s
Details
docker / lint (push) Successful in 40s
Details
test / test (push) Successful in 42s
Details
lint / lint (push) Successful in 44s
Details
docker / lint (pull_request) Successful in 44s
Details
lint / lint (pull_request) Successful in 42s
Details
docker / docker (push) Successful in 46s
Details
1ca5bcbc6b 
The repo already has a write:package REGISTRY_TOKEN secret (used by docker.yml).
Reuse it for uv publish instead of requiring new GITEA_PACKAGE_* secrets:
authenticate as GITHUB_ACTOR with the token as password. Update packaging docs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Latte merged commit da66200be7 into dev 2026-06-27 12:49:18 +00:00
Latte deleted branch feat/publish-reuse-registry-token 2026-06-27 12:49:18 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Compat/Breaking
Breaking change, not backwards compatible
 Kind/Bug
Something is not working
 Kind/Chore
Maintenance, deps, CI/CD
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Refactor
Code restructuring, no behavior change
 Kind/Security
Security-related issue
 Priority/Critical
Must be addressed immediately
 Priority/High
Important, address soon
 Priority/Low
Nice to have
 Priority/Medium
Normal priority
 Reviewed/Confirmed
Issue has been confirmed
 Reviewed/Duplicate
Already tracked elsewhere
 Reviewed/Won't Fix
Acknowledged but won't be addressed
 Status/Blocked
Blocked by an external dependency
 Status/In Progress
Currently being worked on
 Status/Need More Info
Needs more information to proceed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Bartender (Bartender) Latte (Latte)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Hiddenden/AegisGitea-MCP#60
Delete Branch "feat/publish-reuse-registry-token"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?