ci: configure release authentication
Release / release (push) Successful in 3m33s
CI / build (push) Successful in 2m48s

This commit is contained in:
dmg
2026-08-01 11:51:55 -04:00
parent 12c0313947
commit ccac20fa2b
2 changed files with 4 additions and 4 deletions
+3 -3
View File
@@ -15,7 +15,7 @@ jobs:
uses: actions/checkout@v4 uses: actions/checkout@v4
with: with:
fetch-depth: 0 fetch-depth: 0
token: ${{ secrets.GITEA_TOKEN }} token: ${{ secrets.RELEASE_TOKEN }}
- name: Set up Java - name: Set up Java
uses: actions/setup-java@v4 uses: actions/setup-java@v4
@@ -43,7 +43,7 @@ jobs:
- name: Run semantic-release - name: Run semantic-release
env: env:
GITHUB_TOKEN: ${{ secrets.GITEA_TOKEN }} GITHUB_TOKEN: ${{ secrets.RELEASE_TOKEN }}
run: | run: |
npx -y \ npx -y \
-p semantic-release \ -p semantic-release \
@@ -93,7 +93,7 @@ jobs:
- name: Create Gitea release and upload plugin - name: Create Gitea release and upload plugin
if: steps.release.outputs.created == 'true' if: steps.release.outputs.created == 'true'
env: env:
GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }} GITEA_TOKEN: ${{ secrets.RELEASE_TOKEN }}
GITEA_SERVER_URL: ${{ github.server_url }} GITEA_SERVER_URL: ${{ github.server_url }}
REPOSITORY: ${{ github.repository }} REPOSITORY: ${{ github.repository }}
TAG: ${{ steps.release.outputs.tag }} TAG: ${{ steps.release.outputs.tag }}
+1 -1
View File
@@ -114,7 +114,7 @@ Gitea Actions runs the Gradle checks for every push and pull request and stores
- `feat:` creates a minor release; - `feat:` creates a minor release;
- a breaking-change footer or `!` creates a major release. - a breaking-change footer or `!` creates a major release.
A successful release creates a `vX.Y.Z` tag and attaches `spigot-event-producer-X.Y.Z.jar` permanently to the corresponding Gitea Release. The release workflow requires a repository secret named `GITEA_TOKEN` with repository contents write permission. A successful release creates a `vX.Y.Z` tag and attaches `spigot-event-producer-X.Y.Z.jar` permanently to the corresponding Gitea Release. The release workflow requires a repository secret named `RELEASE_TOKEN` with repository contents write permission.
For a local versioned build: For a local versioned build: