chore: notarized-release toolchain and CI fix - #5
Merged
Conversation
Mirror the notarized-release pipeline merged into MBox-Explorer: - scripts/release.sh: archive → export (Developer ID) → DMG → notarize → staple → verify, driven by SCHEME/APP_NAME/TEAM_ID and the RSYNCGUI_NOTARY notary keychain profile. - scripts/ExportOptions.plist: developer-id export with team QRRCB8HB3W. - RELEASE.md: one-time setup + release instructions. - README Installation: DMG steps plus the Gatekeeper workaround (macOS 14 Control-click→Open vs 15/26 System Settings→Privacy & Security→Open Anyway, plus xattr quarantine removal) and a From Source section. - .github/workflows/build.yml: run `xcodebuild test` for the RsyncGUI scheme with code signing disabled. RsyncGUI is pure Swift — its AI insights talk to Ollama/MLX over HTTP and it compiles no mlx-swift dependency — so the Metal Toolchain step is omitted from both the README and CI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QrPsErCe9kBuRRPyDSA5cF
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
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.
Adds a notarized-release toolchain and fixes CI for RsyncGUI, mirroring the pattern merged into
kochj23/MBox-Explorermain.What's included
scripts/release.sh— archive → export (Developer ID) → DMG → notarize → staple → verify. Configured viaSCHEME/APP_NAME=RsyncGUI,TEAM_ID=QRRCB8HB3W, and theRSYNCGUI_NOTARYnotary keychain profile.scripts/ExportOptions.plist—developer-idexport, teamQRRCB8HB3W.RELEASE.md— one-time setup (Developer ID cert + notary profile) and release instructions.xattr -dr com.apple.quarantine), and a From Source section..github/workflows/build.yml— now runsxcodebuild testfor theRsyncGUIscheme withCODE_SIGNING_ALLOWED=NO CODE_SIGNING_REQUIRED=NO. Existingmain/mastertriggers preserved.MLX / Metal Toolchain
RsyncGUI is pure Swift with no third-party Swift packages — its AI insights call out to Ollama/MLX over HTTP (localhost), and there is no
mlx-swiftdependency orimport MLXanywhere. The Metal Toolchain step is therefore omitted from both the README and CI (it would only slow CI without being needed).Detected settings
RsyncGUI.xcodeproj· Scheme:RsyncGUIDEVELOPMENT_TEAMwas empty inproject.pbxproj→ using fallback teamQRRCB8HB3WValidation
bash -n scripts/release.sh✅plutil -lint scripts/ExportOptions.plist→ OK ✅🤖 Generated with Claude Code