ci: use built-in Gitea Actions token for release publish
Drops the need for a manually-managed RELEASE_TOKEN secret; adds contents:write permission so github.token can create the release.
This commit is contained in:
@@ -5,6 +5,9 @@ on:
|
|||||||
tags:
|
tags:
|
||||||
- 'v*.*.*'
|
- 'v*.*.*'
|
||||||
|
|
||||||
|
permissions:
|
||||||
|
contents: write
|
||||||
|
|
||||||
jobs:
|
jobs:
|
||||||
build:
|
build:
|
||||||
runs-on: windows
|
runs-on: windows
|
||||||
@@ -70,7 +73,7 @@ jobs:
|
|||||||
- name: Publish Gitea release
|
- name: Publish Gitea release
|
||||||
shell: pwsh
|
shell: pwsh
|
||||||
env:
|
env:
|
||||||
TOKEN: ${{ secrets.RELEASE_TOKEN }}
|
TOKEN: ${{ github.token }}
|
||||||
run: |
|
run: |
|
||||||
$ver = '${{ steps.ver.outputs.version }}'
|
$ver = '${{ steps.ver.outputs.version }}'
|
||||||
$tag = "v$ver"
|
$tag = "v$ver"
|
||||||
|
|||||||
Reference in New Issue
Block a user