You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Release pipeline: mac-only DMG surface, brew tap, update-impact warnings
- release-core.yml: comment out Windows build + publish; publish only the
4-asset macOS set (dmg + zip + blockmap + latest-mac.yml) that
electron-updater requires; runtime binaries still build as app sidecars
but are no longer published as release assets
- validators: add ade-orchestrator to bundledAgentSkills (mac + win)
- new update install impact probe (connected phones via sync status,
in-process + runtime-backed) surfaced in the pre-install confirm and the
quit dialog, with ADE Code / agent-session disconnect copy
- scripts/update-brew-tap.sh + /release skill phase 8 updated for mac-only
assets and post-publish cask bump; README gets brew install command
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Close isolated-brain gap, automate brew tap bump, scrub stale headless-install docs
- isolated recovery now re-attempts the service install (60s cooldown) when
the primary-socket probe fails, instead of probing forever against a
socket nothing will ever bind; regression test added
- runtimeMode (primary|isolated) exposed in LocalRuntimeStatus, shown in
Settings > About, and surfaced via native notifications on degrade/restore
- update-brew-tap.yml bumps the arul28/homebrew-ade cask on release publish
using a write deploy key (HOMEBREW_TAP_DEPLOY_KEY secret, already set)
- ade-cli README / ARCHITECTURE / remote-runtime docs now state that runtime
release assets are unpublished and SSH bootstrap uses bundled sidecars
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* ship: iter 1 — address review (phone filter, isolated-recovery race, brew-tap robustness)
- main.ts: use canonical phone convention (deviceType "phone" AND platform
"iOS") for update-impact warning, matching the phone device list + APNS
targeting (Greptile P1 / CodeRabbit).
- localRuntimeConnectionPool: confirm the isolated connection is still current
before clearing the recovery timer, so a raced connection swap can't strand
the pool in "isolated" mode with no retry (CodeRabbit).
- update-brew-tap.sh: portable in-place sed, repo-local git identity for the
fallback commit, and a loud guard if the cask substitution silently no-ops
(Greptile P2 / CodeRabbit).
- update-brew-tap.yml: same silent-no-op guard after the sed bumps.
- release SKILL.md: align the Phase 5 draft-asset expectation to the mac-only set.
Declined: pinning GitHub's SSH host key in update-brew-tap.yml — ssh-keyscan to
github.com from a GitHub-hosted runner is standard and low-risk; pinning adds a
key-rotation maintenance burden that can itself silently break the auto-bump.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Expected asset set when `scope.desktop=true` (releases are macOS-only right now;
469
+
Windows publishing is commented out in `release-core.yml`):
469
470
- `ADE-<version>-universal.dmg`
470
471
- `ADE-<version>-universal-mac.zip`
471
472
- `ADE-<version>-universal-mac.zip.blockmap`
472
473
- `latest-mac.yml`
473
-
- `ADE-<version>-win-x64.exe`
474
-
- `ADE-<version>-win-x64.exe.blockmap`
475
-
- `latest.yml`
476
474
477
-
If any macOS asset is missing → mac build or upload broke; re-inspect the `build-mac-release` job.
478
-
If any Windows asset is missing → `build-win-release` broke or its artifact upload failed; re-inspect that job. Do not flip the draft if Windows artifacts are missing — shipping an asymmetric desktop release will confuse electron-updater consumers on the missing platform.
475
+
These four are the complete set — the zip + blockmap + `latest-mac.yml` are what
476
+
electron-updater consumes for auto-update (macOS updates install from the zip,
477
+
not the DMG), so a release missing any of them silently bricks auto-update.
478
+
If any asset is missing → mac build or upload broke; re-inspect the `build-mac-release` job.
0 commit comments