ci: 跳过 dry-run 阶段需要签名的桌面构建#4
Merged
Merged
Conversation
This was referenced May 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
变更摘要
为 ApeCloud fork 的 release dry-run 跳过当前没有签名证书的 Desktop 签名任务，让 release workflow 先验证 CLI、Linux Desktop 和安装脚本产物。
只修改
.github/workflows/release.yml：releasejob 的needs，只汇总build-cli、install-script、bundle-desktop-linux验证方式
本地查看 diff，确认只改 release workflow：
后续验证方式：合并后推测试 tag
v1.35.0-apecloud.0，观察 GitHub Actions release dry-run 是否生成 CLI、Linux Desktop、download_cli.sh和 Docker 镜像。关联 Issue
关联：#3
改动边界
属于「ApeCloud 自己的打包和分发」改动。没有修改 Rust 代码、核心 Agent Loop、MCP runtime、provider 接入或默认功能逻辑。
截图 / Demo（涉及 UI 时填写）
不涉及产品 UI。