Repository navigation
Build, notarize and publish v0.3.1 #182
Copy link
Copy link
Closed
Labels
ready-for-humanRequires the maintainer (real data, devices, accounts)Requires the maintainer (real data, devices, accounts)
Description
Goal
Build, notarize and publish v0.3.1, which ships the #180 fix (PR #181), following ADR 0006 and the v0.3.0 receipt in #169.
Context
- Contents since v0.3.0: Restore pending request review after time away #181 (pending approvals after time away), already code-reviewed and verified on the maintainer's two-display Mac from a Local build of
f99baf7. Not included: Polish approval cards after the v0.3.0 review #176, Return a specific error when an agent creates a duplicate name #179, Fix issues deferred from the v0.2.0 pre-release review #158, Store bundle delivery mappings as separate encrypted metadata #137. - The maintainer decided to skip a full independent pre-release review for this one-fix patch. A quick device check of the release build is still required.
Executor: Codex, coordinated through Orca. Every gated step below needs the maintainer's approval, relayed by the coordinator.
Steps
- Version PR:
AskKeyVersion.current=0.3.1, plus a CHANGELOG0.3.1entry (Fixed: open prompt brought forward on the current display; new prompts open on the pointer's display; Esc shows the next request; unanswered requests recorded as expired, not denied; expiry rechecked after wake or unlock). Gate: maintainer approves the merge. - After the merge's push CI is green, tag
v0.3.1on that commit. Gate: maintainer approves the tag push. - Build
Releaseand install it at/Applications/Ask Key.app, moving the current app to the Trash. Launch it with a clean environment, not from a terminal with Orca orCODEX_HOMEvariables. Gate: maintainer approves the install. Quick device check: version 0.3.1, Broker health, 请旨 display name, and one read approval through the installed helper. - Run
package-release.sh --notary-credentialwith the Ask Key release credential (two approvals in Ask Key). Verify all four files, both checksums, staple and Gatekeeper, and that the app inside the DMG has the same CDHash as the installed build. - Create a draft release with bilingual notes in the style of v0.3.0 and upload the four files. Gate: maintainer approves publication. Publish it, re-download
releases/latest/download/AskKey.dmganonymously and verify it, then post a receipt here in the Build, notarize and publish v0.3.0 #169 format.
Acceptance
Release published with all four assets; receipt posted. Signing identity, Team ID and credential contents never appear in GitHub.
Blocked by
None.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
ready-for-humanRequires the maintainer (real data, devices, accounts)Requires the maintainer (real data, devices, accounts)
Activity
luoji-bot commentedon Oct 11, 2026
Release receipt (Codex executor on the maintainer's Mac, with the maintainer's approval relayed through Orca at each gated step). Signing identity, Team ID, notarization credentials and library contents are kept off this issue.
227edf46ee1a24eae0c98777895287c9c35f9596, version PR #183, annotated tagv0.3.1(TaggersudoHG <by331works@gmail.com>). Push CI: bothbuild-and-testandbasic-ui-flowspassed; Swift 1,127 passed, 0 failed, 3 unchanged opt-in skips; Automation 183 passed; required desktop flows 15 passed, 0 failed, 0 skipped.swift build -j 2passed;swift test -j 2 --filter HelperMCPConnectionTests: 4 passed, 0 failed, 0 skipped; product-version Automation tests: 5 passed, 0 failed, 0 skipped; hygiene, module dependencies and diff checks passed. PR CI: both jobs passed; Swift 1,127 passed, 0 failed, 3 opt-in skips, identical to the base; Automation 183 passed; required desktop flows 15 passed, 0 failed, 0 skipped. No full local suite or local desktop E2E was run.ASKKEY_RELEASES_ENABLED=true bash scripts/build-app.sh Release; implicit release gate passed against the exact push CI and tag. Version/build 0.3.1, strict code signatures and hardened runtime verified for the app and helper. Installed at/Applications/Ask Key.appafter quitting the previous app and moving it to the Trash; registered with Launch Services and launched withenv -i. App CDHash69cf55b0104887996d5a5f79b42867833f5ab0ff; helper CDHashcf3c9ec13966ee7ab99c0143206e4e1f54c9f0de.askkey statusreported protocol 1;askkey healthreportedok; SpotlightkMDItemDisplayNamewas 请旨; MCP initialize returnedserverInfo{name: askkey, version: 0.3.1}. The installed helper'srun --wait-for-approval --credential "审批链路测试" ... -- /bin/echo okvisibly waited for approval, then exited 0 and printed onlyok.package-release.sh --notary-credential "App Store Connect API凭证(发布)"completed both approved submissions. App and DMG notarized and stapled. Both checksum files passedshasum -a 256 -c;cmpconfirmed byte-identical stable and versioned DMGs (9,564,187 bytes each), SHA-2566767fca7ea48b626a1c07eb8f8cf8a0f0e64f5e46f2f724b11908c5583585f9c. Independent staple and Gatekeeper checks passed for the DMG and its inner app. A read-only, non-browsing DMG mount showed version 0.3.1 and app CDHash69cf55b0104887996d5a5f79b42867833f5ab0ff, identical to the installed tested build; it was detached afterwards.releases/latest/download/AskKey.dmgand its checksum. Every download was byte-identical to its candidate, both checksum files passed, and the downloaded DMG was accepted by Gatekeeper asNotarized Developer ID.releases/latest/download/AskKey.dmganonymously afterwards: checksum OK,stapler validateworked, and Gatekeeper accepted it asNotarized Developer ID.testmanagerdservice remains untouched; the previous app is in the Trash as requested. The installed 0.3.1 app remains running; worktree/branch release is left to the coordinator.Follow-ups remain #176, #179, #158 and #137.