chore: update CI/CD workflow to use GITHUB_TOKEN instead of GITEA_TOKEN
This commit is contained in:
@@ -51,7 +51,7 @@ jobs:
|
|||||||
with:
|
with:
|
||||||
registry: ${{ env.REGISTRY }}
|
registry: ${{ env.REGISTRY }}
|
||||||
username: ${{ github.actor }}
|
username: ${{ github.actor }}
|
||||||
password: ${{ secrets.GITEA_TOKEN }}
|
password: ${{ secrets.GITHUB_TOKEN }}
|
||||||
|
|
||||||
- name: Extract metadata (tags, labels) for Docker
|
- name: Extract metadata (tags, labels) for Docker
|
||||||
id: meta
|
id: meta
|
||||||
@@ -95,7 +95,7 @@ jobs:
|
|||||||
TAG_NAME=${GITHUB_REF#refs/tags/}
|
TAG_NAME=${GITHUB_REF#refs/tags/}
|
||||||
|
|
||||||
# Fetch the current release
|
# Fetch the current release
|
||||||
RELEASE_JSON=$(curl -s -H "Authorization: token ${{ secrets.GITEA_TOKEN }}" \
|
RELEASE_JSON=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
|
||||||
${{ github.api_url }}/repos/${{ github.repository }}/releases/tags/${TAG_NAME})
|
${{ github.api_url }}/repos/${{ github.repository }}/releases/tags/${TAG_NAME})
|
||||||
|
|
||||||
# Extract Release ID (if it exists)
|
# Extract Release ID (if it exists)
|
||||||
@@ -110,7 +110,7 @@ jobs:
|
|||||||
|
|
||||||
jq -n --arg body "$NEW_BODY" '{body: $body}' | \
|
jq -n --arg body "$NEW_BODY" '{body: $body}' | \
|
||||||
curl -s -X PATCH \
|
curl -s -X PATCH \
|
||||||
-H "Authorization: token ${{ secrets.GITEA_TOKEN }}" \
|
-H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
|
||||||
-H "Content-Type: application/json" \
|
-H "Content-Type: application/json" \
|
||||||
-d @- \
|
-d @- \
|
||||||
${{ github.api_url }}/repos/${{ github.repository }}/releases/${RELEASE_ID}
|
${{ github.api_url }}/repos/${{ github.repository }}/releases/${RELEASE_ID}
|
||||||
|
|||||||
Reference in New Issue
Block a user