Formerly KrillinAI, VideoTranslation and Dubbing Tool for 120+ Languages. Open-source AI workspace for creators, powered by Codex. Video downloader, video translation, create videos, images, audios, and edits with Agents in one place. For your Social Media like YouTube, TikTok, Instagram, etc.
TypeScript agent-skillscodex-clideskop-appdubbingimage-generationlocalizationskillsttsvideo-editingvideo-generationvideo-transcriptionvideo-translation
ci: reuse candidates for release-only changes
Leggettb7ef4f15e1b4
diff --git a/.codex/skills/oc-deploy/SKILL.md b/.codex/skills/oc-deploy/SKILL.mdindex fb7c5fb1..f4d22ae4 100644--- a/.codex/skills/oc-deploy/SKILL.md+++ b/.codex/skills/oc-deploy/SKILL.md@@ -25,7 +25,7 @@ description: 验证、诊断和发布 OpenCreator Desktop,包括本地实际 A5. GitHub 下载和 `gh` 命令设置 `HTTP_PROXY` 与 `HTTPS_PROXY` 为 `http://127.0.0.1:7897`,并先用 `gh auth status` 确认认证身份。GitHub 保存的签名 secrets 会跨 workflow 运行持续存在,不要要求重复上传。6. 不用付费 Release 构建逐次发现问题。一次远端运行首次出现 package、E2E、签名、公证或上传失败时,立即取消仍在运行的付费 sibling jobs,读取该 run 的已生成日志和 artifacts;不得为了拿日志直接 rerun。7. candidate 只能通过 `workflow_dispatch` 从 `master` 运行。正式发布候选必须选择 `target=all`;结束后确认候选身份凭据和全部 artifacts 已生成、`publish` skipped,并确认 tag 和 Release 均未变化。单平台 candidate 只用于诊断,不能提升为 Release。-8. release 只能对已经通过上述门禁和完整 candidate 的精确 commit 创建 tag。tag workflow 必须提升该 candidate 的不可变 artifacts,不得重新执行付费打包。不得在失败后盲目移动 tag;先本地修复、重新通过门禁、master CI 和完整 candidate,再按用户明确授权处理 tag。+8. release 通常只对已经通过上述门禁和完整 candidate 的精确 commit 创建 tag。候选之后若只有 workflow、Release 附件整理、对应测试或发布文档变化,可由 tag workflow 通过祖先关系、完整 compare 和严格白名单复用不可变 artifacts;任何 App、Runtime、依赖或打包输入变化都必须重新通过完整 candidate。tag workflow 不得重新执行付费打包。## 完成标准diff --git a/.codex/skills/oc-deploy/references/runbook.md b/.codex/skills/oc-deploy/references/runbook.mdindex fc63439b..a66fff40 100644--- a/.codex/skills/oc-deploy/references/runbook.md+++ b/.codex/skills/oc-deploy/references/runbook.md@@ -76,7 +76,7 @@ release 是独立授权边界。用户必须明确指定版本并要求发布:1. 确认版本、目标 commit、工作区、`origin/master`、同 commit 本地 preflight 和 master push CI。2. 确认 tag 不存在;已存在时由用户明确决定,不自行覆盖。-3. 确认完整 candidate run 已生成与目标 commit 绑定的身份凭据和全部附件。+3. 确认完整 candidate run 已生成身份凭据和全部附件。通常 candidate 与 tag commit 相同;若只有发布基础设施变化,确认 candidate 是 tag 的祖先,GitHub compare 完整且差异严格限于 workflow、Release 附件整理、对应测试和发布文档白名单。4. 创建并推送一次 tag,监控由 tag 触发的唯一 promotion run。tag workflow 只能下载并校验该 candidate 的 artifacts,不得重新打包、签名、公证或运行 packaged App E2E。5. promotion 失败时读取候选解析、身份凭据或附件校验错误,不通过移动 tag 或重新付费打包绕过。6. 成功后验证 Release 非 draft、附件完整、命名和下载说明正确,并记录被提升的 candidate run。diff --git a/.github/workflows/desktop-release.yml b/.github/workflows/desktop-release.ymlindex d4083a9b..feefa6f0 100644--- a/.github/workflows/desktop-release.yml+++ b/.github/workflows/desktop-release.yml@@ -289,35 +289,71 @@ jobs:- uses: actions/setup-node@v4with:node-version: 22- - name: 查找同一提交的完整候选构建+ - name: 查找可复用的完整候选构建id: candidateenv:GH_TOKEN: ${{ github.token }}GH_REPO: ${{ github.repository }}- CANDIDATE_NAME: opencreator-release-candidate-${{ github.sha }}shell: bashrun: |- run_id="$(- gh api --method GET "repos/$GH_REPO/actions/artifacts" \- -f name="$CANDIDATE_NAME" \- --jq '.artifacts | map(select(.expired == false)) | sort_by(.created_at) | reverse | .[0].workflow_run.id // empty'- )"- if [[ -z "$run_id" ]]; then- echo "::error::提交 $GITHUB_SHA 没有通过 target=all 的完整候选构建。请先从 master 手动运行 OpenCreator Release。"- exit 1- fi+ candidate_run_id=''+ candidate_sha=''+ while IFS=$'\t' read -r run_id run_sha; do+ candidate_name="opencreator-release-candidate-$run_sha"+ artifact_count="$(+ gh api --method GET "repos/$GH_REPO/actions/runs/$run_id/artifacts" \+ -f name="$candidate_name" \+ --jq '[.artifacts[] | select(.expired == false)] | length'+ )"+ [[ "$artifact_count" == "1" ]] || continue++ comparison="$(gh api "repos/$GH_REPO/compare/$run_sha...$GITHUB_SHA")"+ comparison_status="$(jq -r '.status' <<< "$comparison")"+ [[ "$comparison_status" == "identical" || "$comparison_status" == "ahead" ]] || continue+ changed_files="$(jq -r '.files | length' <<< "$comparison")"+ reported_files="$(jq -r '.changed_files' <<< "$comparison")"+ [[ "$changed_files" == "$reported_files" ]] || continue++ invalid_files="$(+ jq -r '.files[].filename' <<< "$comparison" | while IFS= read -r path; do+ case "$path" in+ .github/workflows/desktop-release.yml|\+ apps/desktop/scripts/release-assets.mjs|\+ apps/desktop/test/release-assets.test.mjs|\+ apps/desktop/test/release-workflow.test.mjs|\+ apps/desktop/release-notes/*|\+ docs/operations/opencreator-desktop-release-runbook.md|\+ .codex/skills/oc-deploy/SKILL.md|\+ .codex/skills/oc-deploy/references/runbook.md)+ ;;+ *) printf '%s\n' "$path" ;;+ esac+ done+ )"+ [[ -z "$invalid_files" ]] || continue- run="$(gh api "repos/$GH_REPO/actions/runs/$run_id")"- if [[ "$(jq -r '.event' <<< "$run")" != "workflow_dispatch" \- || "$(jq -r '.head_branch' <<< "$run")" != "master" \- || "$(jq -r '.head_sha' <<< "$run")" != "$GITHUB_SHA" \- || "$(jq -r '.conclusion' <<< "$run")" != "success" \- || "$(jq -r '.path' <<< "$run")" != ".github/workflows/desktop-release.yml" ]]; then- echo "::error::候选构建 $run_id 与当前 tag 的提交或发布工作流不匹配。"+ candidate_run_id="$run_id"+ candidate_sha="$run_sha"+ break+ done < <(+ gh run list \+ --workflow desktop-release.yml \+ --branch master \+ --event workflow_dispatch \+ --status success \+ --limit 50 \+ --json databaseId,headSha \+ --jq '.[] | [.databaseId, .headSha] | @tsv'+ )++ if [[ -z "$candidate_run_id" ]]; then+ echo "::error::当前 tag 没有可复用的完整候选构建。应用构建输入发生变化时,请先从 master 运行 target=all。"exit 1fi- echo "run-id=$run_id" >> "$GITHUB_OUTPUT"- echo "使用已验证候选构建:$run_id"+ echo "run-id=$candidate_run_id" >> "$GITHUB_OUTPUT"+ echo "sha=$candidate_sha" >> "$GITHUB_OUTPUT"+ echo "name=opencreator-release-candidate-$candidate_sha" >> "$GITHUB_OUTPUT"+ echo "使用已验证候选构建:$candidate_run_id ($candidate_sha)"- uses: actions/download-artifact@v4with:github-token: ${{ github.token }}@@ -336,11 +372,11 @@ jobs:with:github-token: ${{ github.token }}run-id: ${{ steps.candidate.outputs.run-id }}- name: opencreator-release-candidate-${{ github.sha }}+ name: ${{ steps.candidate.outputs.name }}path: candidate- name: 校验候选包身份凭据env:- EXPECTED_SHA: ${{ github.sha }}+ EXPECTED_SHA: ${{ steps.candidate.outputs.sha }}EXPECTED_RUN_ID: ${{ steps.candidate.outputs.run-id }}EXPECTED_REPOSITORY: ${{ github.repository }}run: |diff --git a/apps/desktop/test/release-workflow.test.mjs b/apps/desktop/test/release-workflow.test.mjsindex a8cd46e8..fd21d07c 100644--- a/apps/desktop/test/release-workflow.test.mjs+++ b/apps/desktop/test/release-workflow.test.mjs@@ -100,11 +100,15 @@ describe('Desktop release workflow', () => {it('promotes an immutable successful master candidate instead of rebuilding a tag', () => {expect(releaseWorkflow).toContain("if: github.event_name == 'workflow_dispatch'");- expect(releaseWorkflow).toContain('name: 查找同一提交的完整候选构建');- expect(releaseWorkflow).toContain("jq -r '.head_branch'");- expect(releaseWorkflow).toContain("jq -r '.head_sha'");- expect(releaseWorkflow).toContain("jq -r '.conclusion'");+ expect(releaseWorkflow).toContain('name: 查找可复用的完整候选构建');+ expect(releaseWorkflow).toContain('repos/$GH_REPO/compare/$run_sha...$GITHUB_SHA');+ expect(releaseWorkflow).toContain('comparison_status');+ expect(releaseWorkflow).toContain('changed_files');+ expect(releaseWorkflow).toContain('apps/desktop/scripts/release-assets.mjs');+ expect(releaseWorkflow).toContain('当前 tag 没有可复用的完整候选构建');expect(releaseWorkflow).toContain('run-id: ${{ steps.candidate.outputs.run-id }}');+ expect(releaseWorkflow).toContain('name: ${{ steps.candidate.outputs.name }}');+ expect(releaseWorkflow).toContain('EXPECTED_SHA: ${{ steps.candidate.outputs.sha }}');expect(releaseWorkflow).toContain('name: 校验候选包身份凭据');expect(releaseWorkflow).toContain('needs: verify');expect(releaseWorkflow).not.toContain("startsWith(github.ref, 'refs/tags/') || inputs.target == 'all'");diff --git a/docs/operations/opencreator-desktop-release-runbook.md b/docs/operations/opencreator-desktop-release-runbook.mdindex cf265d2d..b519f215 100644--- a/docs/operations/opencreator-desktop-release-runbook.md+++ b/docs/operations/opencreator-desktop-release-runbook.md@@ -46,8 +46,8 @@ pnpm desktop:package3. 先推送版本提交到 `master`,等待同一提交的 CI 通过,再从 `master` 手动运行 `.github/workflows/desktop-release.yml`,并选择 `target=all`。4. 完整候选工作流使用 `macos-15-intel`、`macos-15` 和 `windows-latest` 并行构建三个原生目标平台。macOS 使用正式 Developer ID 签名和 Apple 公证;每个平台都必须通过实际打包应用 E2E。单平台运行只用于诊断,不能用于正式发布。5. 三个平台和 Linux KrillinAI 附件全部成功后,工作流写入绑定 Git commit、workflow run 和仓库的候选身份凭据。候选附件保存于该 workflow run,不允许构建后替换。-6. 候选全绿后才创建并推送 `v<version>` Git tag。标签版本必须与 `apps/desktop/package.json` 完全一致,且 tag 必须指向候选使用的同一 commit。-7. tag 工作流不再重复构建、签名、公证或 E2E;它只查找同一 commit 的成功 `target=all` 候选,复核 run 与身份凭据,下载已验证附件,校验附件白名单并发布 GitHub Release。找不到精确候选时必须失败。+6. 候选全绿后才创建并推送 `v<version>` Git tag。标签版本必须与 `apps/desktop/package.json` 完全一致。通常 tag 指向候选 commit;候选后只有发布 workflow、Release 附件整理脚本、对应测试或发布文档变化时,可以复用原候选。+7. tag 工作流不再重复构建、签名、公证或 E2E;它查找最新的成功 `target=all` 候选,并通过 GitHub compare 确认候选是 tag 的祖先、差异列表完整且全部属于严格的发布基础设施白名单。任何 App、Runtime、依赖或打包输入变化都会拒绝复用并要求新候选。随后工作流复核 run 与候选身份凭据,下载已验证附件,校验附件白名单并发布 GitHub Release。示例: