2 Commits
Author SHA1 Message Date
m3ta-chiron 5e7d693699 build(release): fix gitea config key (gitea_urls) and pin owner/name
giteaurls is not a goreleaser key — the correct one is gitea_urls. The
scp-style origin remote (gitea@host:owner/repo.git) is also an
unreliable source for owner/name derivation, so release.gitea pins
them explicitly.
2026-10-02 13:05:41 +02:00
m3ta-chiron a913baa496 build(release): add giteaurls block so goreleaser targets code.m3ta.dev
GITEA_URL as an env var does nothing in goreleaser v2; the giteaurls
config block is what routes scm releases to the Gitea API. Without it
the publish step fails with: scm releases: invalid URL: "".
2026-10-02 13:04:06 +02:00
+15 -9
View File
@@ -3,10 +3,21 @@ version: 2
project_name: agent-lib
# Releases gehen an die eigene Gitea-Instanz (NICHT GitHub):
# GITEA_URL=https://code.m3ta.dev
# GITEA_TOKEN=<token mit repository-write>
# Repo/Owner werden aus dem origin-Remote abgeleitet
# (gitea@code.m3ta.dev:m3tam3re/agent-lib.git).
# GITEA_TOKEN=<token mit repository-write> als Umgebungsvariable
# Owner/Name sind explizit gesetzt, weil das SCP-Stil-Remote
# (gitea@code.m3ta.dev:m3tam3re/agent-lib.git) fuer die automatische
# Ableitung unzuverlaessig ist.
gitea_urls:
api: https://code.m3ta.dev/api/v1
download: https://code.m3ta.dev
release:
draft: false
prerelease: auto
mode: append
gitea:
owner: m3tam3re
name: agent-lib
before:
hooks:
@@ -43,11 +54,6 @@ archives:
# .../releases/download/<tag>/agent-lib_<os>_<arch>.<ext>
name_template: "{{ .ProjectName }}_{{ .Os }}_{{ .Arch }}"
release:
draft: false
prerelease: auto
mode: append
changelog:
sort: asc
filters: