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 existingREGISTRY_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).
## 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)
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 dev2026-06-27 12:49:18 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Re-applies the publish-workflow credential fix that landed after PR #59 was merged and therefore never reached
dev..gitea/workflows/publish.ymlnow reuses the existingREGISTRY_TOKENpackage secret (the samewrite:packagePATdocker.ymluses) instead of requiring newGITEA_PACKAGE_*secrets. It authenticatesuv publishasGITHUB_ACTORwith the token as password, and fails loudly if the secret is absent.docs/packaging.mdupdated 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
devper the flowHEAD → feature → dev → main.c551b3c).🤖 Generated with Claude Code