s1d3sw1ped_bot
c6f976bb10
Release Tag still used secrets.RELEASE_TOKEN. Prefer the job built-in token with contents: write, same path as vulture. Link: #11 Co-authored-by: s1d3sw1ped_bot <s1d3sw1ped+giteabot@gmail.com> Co-committed-by: s1d3sw1ped_bot <s1d3sw1ped+giteabot@gmail.com>
30 lines
719 B
YAML
30 lines
719 B
YAML
name: Release Tag
|
|
on:
|
|
push:
|
|
tags:
|
|
- '*'
|
|
|
|
jobs:
|
|
release:
|
|
runs-on: ubuntu-latest
|
|
permissions:
|
|
contents: write
|
|
steps:
|
|
- uses: actions/checkout@main
|
|
with:
|
|
fetch-depth: 0
|
|
- run: git fetch --force --tags
|
|
- uses: actions/setup-go@main
|
|
with:
|
|
go-version-file: 'go.mod'
|
|
- uses: goreleaser/goreleaser-action@master
|
|
with:
|
|
distribution: goreleaser
|
|
version: 'latest'
|
|
args: release
|
|
env:
|
|
GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}
|
|
# Prefer Gitea when the runner also injects GITHUB_TOKEN.
|
|
GITHUB_TOKEN: ${{ secrets.GITEA_TOKEN }}
|
|
GORELEASER_FORCE_TOKEN: gitea
|