Repository navigation
Add legacy native update bridge for 2.0.3–2.0.9 clients - #55
Merged
Merged
Conversation
The native Swift 2.0.x and Tauri 1.3.9 updaters are frozen and only read releases/latest/download/latest.json. Electron releases publish just latest-mac.yml, so those clients got a 404 and could not reach 2.0.12. Each release now also ships latest.json, a minisign-signed CCbuddy-<version>-legacy-mac-arm64.app.tar.gz and its .sig. The archive holds the signed Electron app re-signed as dev.ccbud.gateway (the identity the old client requires) with a team-only designated requirement, so the bridge can later accept the normal app.ccbuddy.desktop update through Squirrel. The bridge is notarized and stapled, and latest.json is re-verified against the legacy public key before and after upload. Only arm64 keys are listed; Intel clients fall back to manual download. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017zzyG8j5ALC6AdRu24Zp3c
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.
Summary
Implements a legacy native update bridge to enable CCbuddy 2.0.3–2.0.9 (native Swift) and Tauri 1.3.9 clients to update to the new Electron-based releases. These frozen clients only read
releases/latest/download/latest.jsonwith a hardcoded minisign public key, but Electron releases only publishlatest-mac.yml. This change generates the requiredlatest.jsonmanifest and re-signs the app under the legacy identity so old clients can install and update.Key Changes
legacy-native-update.mjs: Core utility script that:FB130F2908B61575)latest.jsonmanifests with arm64-only platform keys (Intel clients fall back to manual download)write,verify, andcheck-symlinkscommandspackage-legacy-native-bridge.sh: macOS release workflow script that:dev.ccbud.gateway)app.ccbuddy.desktopupdates.approot (old client requirement)latest.jsonbefore publicationlegacy-native-update.test.mjs: Comprehensive test suite covering:Release workflow integration (
.github/workflows/release.yml):latest.json,.tar.gz,.sig) alongside normal Electron assetsDocumentation (
docs/specs/legacy-native-update-bridge.md):Notable Implementation Details
anchor apple generic and certificate leaf[subject.OU] = "2CGR266XD2") so Squirrel.Mac accepts the next normalapp.ccbuddy.desktopupdateMinisignUpdateVerifier: BLAKE2b-512 prehashing with separate global signature verificationData(base64Encoded:)behavior.approot, no absolute paths, no.., and no symlinks escaping the bundlehttps://claude.ai/code/session_017zzyG8j5ALC6AdRu24Zp3c