Skip to content

Build, notarize and publish v0.3.0 #169

Closed

Description

@sudoHG

Goal

Build, notarize, verify and publish v0.3.0, following #105 and #127.

Context

Process: ADR 0006 and the pre-release checks in docs/testing.md. Notarization through the Ask Key credential (package-release.sh --notary-credential).

Contents since v0.2.0: agents write usage instructions and groups (#161, PR #163), agents organize credentials and groups in one approved batch (#162, PR #166), the app shows as 请旨 on Chinese systems (#167, PR #168), and stable-named release assets (#164, PR #165). Not included: #158, #137.

Executor: Planner with the maintainer.

Scope

  1. Independent read-only pre-release review of v0.2.0..main (done 2026-10-08: 2 blockers, 2 should-fix and 1 nit, all fixed in Fix v0.3.0 pre-release review findings in agent group writes #171) before the version PR Prepare the v0.3.0 release #170 merges.
  2. Version PR: AskKeyVersion.current = 0.3.0, CHANGELOG entry.
  3. Tag v0.3.0 on the merged commit once its push CI is green; build Release, install at /Applications/Ask Key.app, walk through the pre-release checks with the maintainer, including 请旨 / Ask Key in Finder and the Touch ID prompt and one real agent run of the new metadata and organize tools with synthetic credentials.
  4. Notarize the same build, upload all four files to a draft release, publish.

Merging the version PR, pushing the tag, installing into /Applications, and publishing each need the maintainer's explicit approval.

Acceptance

Release published with all four assets; receipt posted here as in #105.

Blocked by

#171 (fixes from the pre-release review).

Activity

  1. added
    ready-for-humanRequires the maintainer (real data, devices, accounts)
    on Oct 8, 2026
  2. added a commit that references this issue on Oct 8, 2026
  3. luoji-bot commented on Oct 10, 2026

    @luoji-bot

    Release receipt (planner, on the maintainer's Mac with the maintainer's approval at each gated step). Signing identity, Team ID, notarization credentials and library contents are kept off this issue.

    • Released commit: 3db3fa4, annotated tag v0.3.0. Push CI for that commit: both build-and-test and basic-ui-flows succeeded. The tag was moved twice before publication (from 425e29e and 312fcab) after pre-release fixes; no release existed for those.
    • Pre-release review: independent read-only review of v0.2.0..main, findings fixed in Fix v0.3.0 pre-release review findings in agent group writes #171 (PR Fix agent group write privacy, transactions and cancellation #172). The approval cards were reworked in Make agent approval cards readable at a glance #173/Show which components change in a modify approval #174 (PR Make agent approval cards readable at a glance #175) and returned to the v0.2 layout in Restore the v0.2 approval card style for every card #177 (PR Restore the v0.2 approval card style for every card #178) after device review.
    • Build: build-app.sh Release; release gate passed. Version 0.3.0, hardened runtime. Installed at /Applications/Ask Key.app; tested CDHash fd680cad…, identical to the app inside the published DMG.
    • Device checks (maintainer present): 请旨 shown as the display name; create, modify, organize (9 steps incl. group create, rename, delete), delete ×3, read (value injected, not printed) and a 30-minute allowance (second read ran without a prompt) through the installed helper; Touch ID entries in the app (unlock, reveal/copy, revoke timed allowance, permanent delete, settings); focus returned to the previous app after every agent approval (front-app log); Claude Code connected and read the new {credentials, groups} catalog in a fresh session; Codex MCP enabled.
    • Package: package-release.sh --notary-credential (two approved askkey run submissions). App and DMG notarized, stapled and accepted by Gatekeeper (Notarized Developer ID).
    • Release: v0.3.0 with bilingual notes and four assets. AskKey.dmg and AskKey-0.3.0.dmg are byte-identical, SHA-256 a2b1b1df72e68b1e5b567ae9b8c6e3c0fdafe34e4b12139ec849cf2dea93c253; releases/latest/download/AskKey.dmg re-downloaded anonymously and verified with shasum -a 256 -c.

    Follow-ups: #176 (card polish), #158, #137; a duplicate-name create returns a generic internal_error instead of a specific error (to be filed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-humanRequires the maintainer (real data, devices, accounts)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions