MineDivinity/pack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 25 Wiki Activity

Fix SHA1 checksum file naming in build-and-release workflow

Browse Source
This commit is contained in:
B3ni
2025-06-22 03:02:11 +02:00
parent 117c195e53
commit 696071bbb1
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.gitea/workflows/build-and-release.yml
View File

@ -51,7 +51,7 @@ jobs:
README.md README.md
# Generate SHA1 checksum # Generate SHA1 checksum
sha1sum MineDivinity-Pack.zip > MineDivinity-Pack.zip.sha1 sha1sum MineDivinity-Pack.zip > MineDivinity-Pack.sha1.txt
echo "ZIP file created: MineDivinity-Pack.zip" echo "ZIP file created: MineDivinity-Pack.zip"
echo "SHA1 checksum generated" echo "SHA1 checksum generated"
@ -107,7 +107,7 @@ jobs:
-X POST \ -X POST \
-H "Authorization: token ${{ secrets.TOKEN }}" \ -H "Authorization: token ${{ secrets.TOKEN }}" \
-H "Content-Type: text/plain" \ -H "Content-Type: text/plain" \
--data-binary @MineDivinity-Pack.zip.sha1 \ --data-binary @MineDivinity-Pack.sha1.txt\
"${{ steps.create-release.outputs.upload_url }}?name=MineDivinity-Pack.zip.sha1" "${{ steps.create-release.outputs.upload_url }}?name=MineDivinity-Pack.sha1.txt"
echo "Artifacts uploaded successfully" echo "Artifacts uploaded successfully"