[theoephraim]

Published artifacts no longer depend on any build cache, and the remaining rharkor/caching-for-turbo users move to the secret-gated Depot turbo cache.

• Release path builds from source: the npm publish and binary release jobs in release.yaml, binary-release.yaml, and notarize-native-macos.yaml drop the turbo cache. Their GitHub cache rarely hit anyway now that main builds write to Depot's cache, so the cost is small and releases are infrequent.
• build-native-macos.yaml takes an optional DEPOT_TURBO_TOKEN secret. PR callers (test.yaml, binary-preview.yaml) pass it so Swift PRs reuse the varlock libs build across pushes; release.yaml doesn't, so the release build of the macOS app runs from source.
• nextjs-canary and deploy-tests (scheduled/manual, nothing published) use the Depot turbo cache via the shared action.

[pullfrog]

✅ No new issues found.

Reviewed changes: Reviewed all eight workflow changes, the shared Depot cache action, and the release/preview caller paths.

• Release builds: Removes remote Turbo cache setup from npm publishing, CLI binary releases, and macOS notarization jobs; existing native-binary caches remain unchanged.
• macOS cache gating: Adds an optional Depot token to the reusable build workflow, forwards it from CI/preview callers, and leaves release callers without remote caching.
• Scheduled tests: Moves deployment and Next.js canary builds to the existing secret-gated Depot cache action.

The CI build/test and Actions analysis checks passed. The changed macOS and publishing paths were reviewed statically, not executed in this review.

  ^{｜ View workflow run ｜ Using gpt-6.1-sol ｜ 𝕏}