smtp2shoutrrr/.github/workflows/release.yml
Full-Stack Developer 29e9343460
All checks were successful
CI / goreleaser-lint (pull_request) Successful in 5s
CI / format (pull_request) Successful in 1m22s
CI / lint (pull_request) Successful in 3m37s
CI / test (pull_request) Successful in 3m32s
CI / build (pull_request) Successful in 5m24s
ci: use the goreleaser from the CI image instead of goreleaser-action
goreleaser-action v7.1.0 made cosign signature verification of its own
download mandatory, and ci-base ships no cosign — the goreleaser-lint
job failed on the v6.4.0 -> v7.2.3 bump.

The action was redundant anyway: ci-base already installs goreleaser
from the upstream apt repo, which is what `make build` has always used.
Both workflows now call it directly, and `goreleaser check` moves behind
a `make check` target so every CI job runs a make target.

Co-authored-by: multica-agent <github@multica.ai>
2026-09-07 16:54:09 +00:00

28 lines
677 B
YAML

name: Release
on:
push:
tags: ["v*"]
jobs:
release:
runs-on: docker
container: git.nakama.town/fmartingr/ci-images/ci-base:1.0.0
steps:
- uses: actions/checkout@v7
with:
fetch-depth: 0
- name: Install Go
uses: actions/setup-go@v7
with:
go-version-file: go.mod
- name: Login to container registry
run: echo "${{ secrets.FORGEJO_TOKEN }}" | docker login git.nakama.town -u ${{ github.actor }} --password-stdin
- name: Run GoReleaser
run: goreleaser release --clean
env:
GORELEASER_FORCE_TOKEN: gitea
GITEA_TOKEN: ${{ secrets.FORGEJO_TOKEN }}