octoturge
9798b522bd
GITEA_PACKAGE_TOKEN was never a creatable secret name (GITEA_ prefix is reserved), and Gitea Actions' built-in token can be granted registry write access directly via `permissions: packages: write` (per https://docs.gitea.com/usage/actions/token-permissions/) - the "unauthorized: reqPackageAccess" issue noted earlier looks to have been exactly this: the default restricted token mode denying package write unless a job explicitly requests it, not an unfixable bug in the token itself. Drops the manual-PAT requirement entirely - no secret to create or maintain.