public/supaspin
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fix: write the repository's real address in the docs

Browse Source 
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>
This commit was merged in pull request #6.
This commit is contained in:
Igor
2026-09-22 21:58:53 +03:00
co-authored by Claude Opus 5
parent 1d49234400
commit 99fdf7a0ab
5 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+7 -1
View File
@@ -21,8 +21,14 @@ The number is `MAJOR.MINOR.PATCH` (semantic versioning: `1.1.1` is major 1, mino
4. **Tag every release.** After the pull request is merged, create the git tag `vX.Y.Z` (for example `v1.1.1`) on
the commit on `main` that contains that number in `VERSION`. The tag name must equal `VERSION` with a `v` in
front. A version without a tag is not released. Never move or delete a tag that was already published; if a
release is wrong, ship a new PATCH instead. With the Gitea API: `POST /api/v1/repos/igor/supaspin/tags` with
release is wrong, ship a new PATCH instead. With the Gitea API: `POST /api/v1/repos/public/supaspin/tags` with
`tag_name`, `target` (the commit) and `message`.
The owner in an API address must be `public`. The repository used to sit under the user `igor` and Gitea still
forwards the old address for anything a browser or git does, but it answers an API call to
`/api/v1/repos/igor/supaspin/...` with a redirect that curl does not follow for a POST: the command returns an
empty body and no error, which looks exactly like a rejected token. Opening or merging a pull request needs the
same `public` owner.
5. **Check the result.** Reinstall from the merged `main` (`sudo bash install.sh`), then run `supaspin --version` and
compare it with `VERSION` and the tag.
6. If you find a version in `VERSION` that has no tag, or a tag that does not match `VERSION`, tell Igor before doing