fix z s3 upload path

This commit is contained in:
xopenwrt 2026-06-28 22:27:29 +08:00
parent 13e85ab847
commit 175b2680b4
2 changed files with 13 additions and 1 deletions

View File

@ -319,7 +319,7 @@ jobs:
- name: 2 Upload SP_UEFI_VMDK to SharePoint - name: 2 Upload SP_UEFI_VMDK to SharePoint
uses: xopenwrt/s3-upload-github-action@master uses: xopenwrt/s3-upload-github-action@master
env: env:
FILE: ./${{ steps.date.outputs.date }}e/${{ env.SP_UEFI_VMDK }} FILE: ./${{ steps.date.outputs.date }}/${{ env.SP_UEFI_VMDK }}
S3_ENDPOINT: 's3.openwrt.115115.xyz' S3_ENDPOINT: 's3.openwrt.115115.xyz'
S3_BUCKET: ${{ secrets.S3_BUCKET }} S3_BUCKET: ${{ secrets.S3_BUCKET }}
S3_ACCESS_KEY_ID: ${{ secrets.S3_ACCESS_KEY_ID }} S3_ACCESS_KEY_ID: ${{ secrets.S3_ACCESS_KEY_ID }}

View File

@ -0,0 +1,12 @@
# AI Modification Log: Z S3 Upload Path
Date: 2026-06-28
## Change
- Fixed the Z workflow UEFI VMDK S3 upload path in `.github/workflows/X-x86_64_Z.yml`.
- Changed `./${{ steps.date.outputs.date }}e/${{ env.SP_UEFI_VMDK }}` to `./${{ steps.date.outputs.date }}/${{ env.SP_UEFI_VMDK }}`.
## Reason
The extra `e` after the date output made the upload action look in a non-existent directory, causing the UEFI VMDK upload to miss the generated firmware artifact.