| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
ci: build the portable .app in the release workflow The release workflow ran `make bundle`, which produces a lean .app (binary + ldid + signcert + icon only) — missing the bundled scripts/patchers/resources/ requirements.txt/vphoned/.tools — so published release assets were not self-contained and `brew install` copies couldn't run the fw/restore/cfw pipeline. Switch to ./scripts/build.sh (the canonical portable build): - also init the scripts/resources storage submodule + the scripts/repos/{trustcache,insert_dylib} tool sources - build .tools/bin/{trustcache,insert_dylib} (mirrors setup_tools steps 2-3; its venv + sshpass steps aren't needed to build) - run build.sh, then fail the job if the bundle is missing any runtime asset or the virtualization entitlement before packaging + uploading Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y4VDqWf5pVakcFLqB23CKe | 1 个月前 |