The repository is owned by the organisation public, not the user igor. Gitea forwards the old address for browsers and git, so the install and clone commands kept working and nobody noticed.
An API call is the exception: a POST to /api/v1/repos/igor/supaspin/... is answered with a redirect curl does not follow for a POST, so it returns an empty body and no error - which reads as a rejected token. Creating the v1.2.0 tag and opening its pull request both failed this way first.
CLAUDE.md: the tagging rule names public and says why an API address cannot use the forwarded one.
README.md, install.sh: install, token and clone commands use the address the server actually serves.
Version 1.2.0 -> 1.2.1. No change to what the program does.
The repository is owned by the organisation `public`, not the user `igor`. Gitea forwards the old address for browsers and git, so the install and clone commands kept working and nobody noticed.
An API call is the exception: a POST to `/api/v1/repos/igor/supaspin/...` is answered with a redirect curl does not follow for a POST, so it returns an empty body and no error - which reads as a rejected token. Creating the v1.2.0 tag and opening its pull request both failed this way first.
- `CLAUDE.md`: the tagging rule names `public` and says why an API address cannot use the forwarded one.
- `README.md`, `install.sh`: install, token and clone commands use the address the server actually serves.
Version 1.2.0 -> 1.2.1. No change to what the program does.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The repository is owned by the organisation `public`, not by the user `igor`.
Gitea forwards the old address for anything a browser or git does, so the install
command and the clone lines kept working and the wrong address went unnoticed.
An API call is the exception. A POST to `/api/v1/repos/igor/supaspin/...` is
answered with a redirect that curl does not follow for a POST, so the command
returns an empty body and no error - which reads as a rejected token. Creating
the v1.2.0 tag and opening its pull request both failed this way first.
- CLAUDE.md: the tagging rule now names `public` and says why an API address
cannot use the forwarded one.
- README.md, install.sh: the install, token and clone commands now use the
address the server actually serves.
Version 1.2.0 -> 1.2.1. No change to what the program does.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
igor
merged commit 99fdf7a0ab into main2026-09-22 18:59:05 +00:00
igor
deleted branch fix/repository-address-in-docs2026-09-22 18:59:05 +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.
The repository is owned by the organisation
public, not the userigor. Gitea forwards the old address for browsers and git, so the install and clone commands kept working and nobody noticed.An API call is the exception: a POST to
/api/v1/repos/igor/supaspin/...is answered with a redirect curl does not follow for a POST, so it returns an empty body and no error - which reads as a rejected token. Creating the v1.2.0 tag and opening its pull request both failed this way first.CLAUDE.md: the tagging rule namespublicand says why an API address cannot use the forwarded one.README.md,install.sh: install, token and clone commands use the address the server actually serves.Version 1.2.0 -> 1.2.1. No change to what the program does.
🤖 Generated with Claude Code