Hiddenden/familiar
5
0 Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
38 Commits 2 Branches 0 Tags
eb2922f63c1621e46e43c0f71128712c4a251251
Commit Graph
5 Commits
Author SHA1 Message Date
Latte eb2922f63c ci(docker): build, smoke-test, and publish the remote-HTTP image 
New .gitea/workflows/docker.yml (alongside the untouched ci.yml wheel publish).
Runs lint + test, then builds the image and smoke-tests it — non-root uid,
/healthz 200, MCP 401 without a token and 200 with a valid bearer. On a merge to
main/dev it pushes to git.hiddenden.cafe/hiddenden/familiar (main -> :latest +
:main, dev -> :dev, plus :sha-<12>) via the existing REGISTRY_TOKEN, then does a
scoped cleanup. The two workflows are independent and don't interfere.
 2026-07-04 19:26:17 +02:00
LatteandClaude Opus 4.8 edf2298e20 ci: authenticate twine with REGISTRY_TOKEN secret
CI / lint (pull_request) Successful in 51s
Details
CI / test (pull_request) Successful in 59s
Details
CI / lint (push) Successful in 53s
Details
CI / publish (pull_request) Has been skipped
Details
CI / test (push) Successful in 1m0s
Details
CI / publish (push) Successful in 51s
Details 
The repo already has a REGISTRY_TOKEN secret (Gitea access token with
package scope); the workflow referenced a non-existent PACKAGE_REGISTRY_TOKEN
and fell back to the auto GITHUB_TOKEN, which is not granted package-write,
so every upload was rejected. Point twine at REGISTRY_TOKEN.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-06-27 18:01:22 +02:00
LatteandClaude Opus 4.8 d76c8f87a8 ci: drop unsupported --skip-existing from twine upload
CI / lint (pull_request) Successful in 51s
Details
CI / test (pull_request) Successful in 59s
Details
CI / lint (push) Successful in 52s
Details
CI / publish (pull_request) Has been skipped
Details
CI / test (push) Successful in 58s
Details
CI / publish (push) Failing after 30s
Details 
Gitea's PyPI registry rejects twine's --skip-existing flag
(UnsupportedConfiguration), which failed every publish run. Remove it and
instead tolerate an "already exists" conflict in the shell, so dev (unique
.devN versions) always publishes and a main re-run of an existing release
is treated as success rather than a hard failure.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-06-27 17:57:50 +02:00
LatteandClaude Opus 4.8 a136853126 ci: grant contents:read so publish can checkout private repo
CI / lint (pull_request) Successful in 52s
Details
CI / test (pull_request) Successful in 58s
Details
CI / publish (pull_request) Has been skipped
Details
CI / lint (push) Successful in 51s
Details
CI / test (push) Successful in 56s
Details
CI / publish (push) Failing after 29s
Details 
Setting `permissions: packages: write` alone dropped every other scope to
none, so actions/checkout could not clone the private repo and the publish
job failed before building. Add contents:read, and use github.actor (more
reliably populated than gitea.actor) as the twine username.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-06-27 17:52:14 +02:00
LatteandClaude Opus 4.8 585acc766c ci: add Gitea Actions workflow (lint, test, publish)
CI / lint (pull_request) Successful in 53s
Details
CI / test (pull_request) Successful in 1m0s
Details
CI / publish (pull_request) Has been skipped
Details
CI / lint (push) Successful in 53s
Details
CI / test (push) Successful in 59s
Details
CI / publish (push) Failing after 39s
Details 
Lint (ruff) and test (pytest, fail under 80% coverage) on every PR and
push to main/dev. On a merge to main/dev, build the sdist+wheel and
publish to the Gitea PyPI registry — main as a clean release, dev as a
unique .devN pre-release. No Docker; runs on uv.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-06-27 17:34:59 +02:00