refactor: use variable for release notes in GitHub and Gitea release workflows
This commit is contained in:
1 parent
004406a3f3
commit
e26974ac65
2 files changed
+9
-2
No files matched your search
@@ -148,6 +148,7 @@ jobs:
|
||||
GITEA_API_URL: ${{ steps.gitea_url.outputs.GITEA_API_URL }}
|
||||
GITEA_REPO: ${{ steps.gitea_url.outputs.GITEA_REPO }}
|
||||
GITEA_OWNER: ${{ steps.gitea_url.outputs.GITEA_OWNER }}
|
||||
CHANGES: ${{ steps.release_notes.outputs.CHANGES }}
|
||||
run: |
|
||||
# Debug Token (nur Länge ausgeben für Sicherheit)
|
||||
echo "Debug: Token length: ${#GITEA_TOKEN}"
|
||||
@@ -165,7 +166,12 @@ jobs:
|
||||
|
||||
# Erstelle zuerst den Release ohne Dateien
|
||||
echo "Debug: Creating release..."
|
||||
RELEASE_DATA="{\"tag_name\":\"v${VERSION}\",\"name\":\"v${VERSION}\",\"body\":\"${{ steps.release_notes.outputs.CHANGES }}\"}"
|
||||
# Verwende jq für sicheres JSON-Building
|
||||
RELEASE_DATA=$(jq -n \
|
||||
--arg tag "v${VERSION}" \
|
||||
--arg name "v${VERSION}" \
|
||||
--arg body "$CHANGES" \
|
||||
'{tag_name: $tag, name: $name, body: $body}')
|
||||
|
||||
RELEASE_RESPONSE=$(curl -s -w "\n%{http_code}" \
|
||||
-X POST \
|
||||
|
||||
@@ -119,6 +119,7 @@ jobs:
|
||||
- name: Create GitHub Release
|
||||
env:
|
||||
GH_TOKEN: ${{ secrets.RELEASE_TOKEN }}
|
||||
RELEASE_NOTES: ${{ steps.release_notes.outputs.CHANGES }}
|
||||
run: |
|
||||
VERSION=${{ steps.get_version.outputs.VERSION }}
|
||||
cd .pio/build/esp32dev
|
||||
@@ -144,7 +145,7 @@ jobs:
|
||||
if [ -n "$FILES_TO_UPLOAD" ]; then
|
||||
gh release create "v${VERSION}" \
|
||||
--title "Release ${VERSION}" \
|
||||
--notes "${{ steps.release_notes.outputs.CHANGES }}" \
|
||||
--notes "$RELEASE_NOTES" \
|
||||
$FILES_TO_UPLOAD
|
||||
else
|
||||
echo "Error: No files found to upload"
|
||||
|
||||
Reference in new issue
Block a user