[Bug] gateway 进程下载前端资产失败

[MelodyUSA]

💻 系统环境 | Operating System

Ubuntu

🌐 浏览器 | Browser

Chrome

🐛 问题描述 | Bug Description

docker compose 日志

$ docker compose logs -f ppanel-service
ppanel-service  | 2026/05/27 23:36:15 [Info] <调度器> 初始化 | 任务调度器已初始化 - ../home/runner/work/updater/updater/core/scheduler/scheduler.go:19
ppanel-service  | 2026/05/27 23:36:15 [Info] <基础模块> 服务启动 | 日志级别：info - ../home/runner/work/updater/updater/gateway.go:27
ppanel-service  | 2026/05/27 23:36:18 [Error] <GitHub工具> 获取资产链接 | 获取仓库 perfect-panel/frontend 资产 admin-web-with-api 链接失败: 未找到名为 admin-web-with-api 的资产 - ../home/runner/work/updater/updater/core/utils/github.go:200
ppanel-service  | 2026/05/27 23:36:18 [Error] <基础模块> Admin静态模块 | 文件不存在，且下载失败：未找到名为 admin-web-with-api 的资产 - ../home/runner/work/updater/updater/gateway.go:85
ppanel-service  | panic: 未找到名为 admin-web-with-api 的资产
ppanel-service  | 
ppanel-service  | goroutine 1 [running]:
ppanel-service  | main.main()
ppanel-service  | 	/home/runner/work/updater/updater/gateway.go:86 +0x1616

请问 gateway 下载前端资产的目标地址是这里吗 https://github.com/perfect-panel/frontend/releases
docker 部署后，一直下载失败，是不是因为新 releases 打包错误啦？
新的 releases 只有源码

🚦 期望结果 | Expected Behavior

No response

📷 复现步骤 | Recurrence Steps

No response

📝 补充信息 | Additional Information

No response

[web-ppanel]

Hi @MelodyUSA,

Thank you for reporting this issue.

After investigation, the root cause is that v1.6.3 was created as a manual tag on a merge commit, which caused semantic-release to skip the release process (no assets were uploaded).

Analysis:

• v1.6.2 has the correct assets: ppanel-admin-web-with-api.tar.gz
• v1.6.3 was created from PR fix: show purchased subscriptions regardless of plan visibility #66 merge commit (0fd7973), but semantic-release detected "0 commits since last release" and skipped the prepare/publish steps
• The workflow log shows: There are no relevant changes, so no new version is released.

This is an infrastructure/CI issue, not a frontend code bug. The release workflow needs to be fixed by repository maintainers to ensure assets are properly uploaded.

Workaround for now:
You can use v1.6.2 assets, or wait for the next proper release.

Closing this as it's outside the scope of the frontend codebase.