zqlit
80ea1ff5b3
Deploy to Production / pre-check (push) Successful in 2m6s
Deploy to Production / build (push) Successful in 4m18s
Deploy to Production / deploy-edgeone (push) Successful in 7s
Deploy to Production / finalize (push) Successful in 16s
Deploy to Production / notify-failure (push) Skipped
deploy-upyun 是零上传动作的空壳 job，却无条件打印「UpYun 已同步最新内容」，其输出被 Telegram / 飞书 / 邮件通知当成 UpYun 部署成功的依据；真正的上传步骤标了 continue-on-error，失败也不影响 job 颜色。三层叠加，导致 7/25 起国内线路停更两个多月而通知始终显示成功。 改动：删除 deploy-upyun（finalize / notify-failure 的 needs 同步清理）；Upload to UpYun 在退出时写 GITHUB_OUTPUT，如实上报 success / failure / skipped 三态与真实耗时（不用 steps.outcome，只依赖最通用的 output 传递）；通知与 Step Summary 改为展示三态真实结果，移除「文件已在 Build 阶段同步」这类未经验证的说法。 又拍云直传失败仍不阻断流水线 —— 国内线路由腾讯云广州的 1Panel 计划任务「又拍云同步(国内中转)」每分钟兜底增量推送。