Felix FaerberandClaude Opus 5 70786f73ab push with a write:package token, not the Actions token ...

Second build failed the same way: docker login to this instance's registry
returns "unauthorized" for the automatic Actions token, and declaring
permissions: packages: write did not change it -- Gitea's task token is accepted
by the API but not by the package registry.

So the push uses REGISTRY_TOKEN, an org secret holding a personal access token
scoped to write:package and nothing else. The step fails with that sentence in
the log rather than another bare "unauthorized", because the difference
between a missing secret and a rejected credential is not visible from the
error docker prints.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CYFnHida4AdiNDek2pzgXx

2026-09-15 12:38:14 +03:00

.gitea/workflows

push with a write:package token, not the Actions token

2026-09-15 12:38:14 +03:00

app

Add chat history sidebar with restore across reloads (#1)

2026-08-19 00:20:30 +03:00

.gitignore

first commit

2026-05-27 12:22:05 +03:00

docker-compose.yml

first commit

2026-05-27 12:22:05 +03:00

Dockerfile

first commit

2026-05-27 12:22:05 +03:00

package-lock.json

first commit

2026-05-27 12:22:05 +03:00

package.json

first commit

2026-05-27 12:22:05 +03:00

react-router.config.ts

first commit

2026-05-27 12:22:05 +03:00

tsconfig.json

first commit

2026-05-27 12:22:05 +03:00

vite.config.ts

first commit

2026-05-27 12:22:05 +03:00

S

Description

No description provided

98 KiB

0 Stars 1 Watchers 0 Forks

Languages

TypeScript 96.3%

Dockerfile 3.1%

CSS 0.6%