| Filename | Latest commit message | Latest commit date |
|---|---|---|
butterrobot
16a1d6cdaa
All checks were successful
Both `secrets.FORGEJO_TOKEN` references in `.github/workflows/release.yml` are now `secrets.ACTIONS_TOKEN`: the registry login password and the `GITEA_TOKEN` handed to GoReleaser. Those were the only two occurrences anywhere in the repository — nothing else, including the README and the goreleaser config, named the secret.
Nothing else about the release job changes: `-u ${{ github.actor }}` and `GORELEASER_FORCE_TOKEN: gitea` are untouched.
## Needs a secret to exist before the next tag
The rename only redirects which secret the job reads. `ACTIONS_TOKEN` has to be defined on the repository (or its owner/org) with the same reach the release needs — `write:package` on `git.nakama.town/fmartingr/`, plus repo write for the release upload — or the release job will get an empty value and repeat the `401 Unauthorized: reqPackageAccess` failure from FMG-5. Note that the login step will still print `Login Succeeded` in that case, for the reason described on #10.
I could not verify the secret exists: `tea actions secret list` refuses for this credential (`user should be the owner of the repo`), and Forgejo does not expose a secret's value, owner, or scopes through the API.
## Checks
CI-config change only, no Go code touched. I parsed both workflow files to confirm they are still valid YAML and that the release job's env block resolves to `GITEA_TOKEN: ${{ secrets.ACTIONS_TOKEN }}`. There is no Go toolchain, golangci-lint, or goreleaser in this environment, so the repository's `format` / `lint` / `test` / `build` / `check` targets were not run locally — CI covers them on this PR.
Closes FMG-6
Reviewed-on: #12
|
||
| .. | ||
| ci.yml | ||
| release.yml | ||