Zakaria El OrcheandClaude Sonnet 5
3f0b49fa36
Publish Maven packages / publish (push) Successful in 1m55s
Root cause of the persistent 401s found: Gitea's own per-job GITEA_TOKEN cannot publish to any package registry at all — a known, still- unimplemented limitation (go-gitea/gitea#23642), not a settings.xml auth-format issue as first assumed. Confirmed by testing: GITEA_TOKEN authenticated fine against the plain API but every registry write endpoint rejected it regardless of scope or header style. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
25 lines
1.3 KiB
XML
25 lines
1.3 KiB
XML
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
|
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
|
|
<!--
|
|
Used only by .gitea/workflows/publish-maven.yml (mvn -s .gitea/maven-settings.xml deploy).
|
|
Not used for local builds. PACKAGES_TOKEN is a real personal access token (write:package
|
|
scope) on the Relism account, read from the env var the workflow exports — never written
|
|
to disk. Deliberately not Gitea's own per-job GITEA_TOKEN: that token can't publish to
|
|
any package registry at all, a known unimplemented limitation
|
|
(https://github.com/go-gitea/gitea/issues/23642) — confirmed here by testing: it
|
|
authenticated fine against the plain API but still got 401 from this endpoint.
|
|
|
|
Basic auth (username/password): the <httpHeaders> form Gitea's own docs show for this is
|
|
honored by Maven's resolver (used for reading <repositories>) but not reliably by the
|
|
wagon-http provider maven-deploy-plugin actually uploads through.
|
|
-->
|
|
<servers>
|
|
<server>
|
|
<id>gitea</id>
|
|
<username>Relism</username>
|
|
<password>${env.PACKAGES_TOKEN}</password>
|
|
</server>
|
|
</servers>
|
|
</settings>
|