ReviewOS

stacks/launchpad

Release Launchpad 1.0.0 through Pantry and the Mac App Store

#6
Open chris opened this 6 days ago ·
6 days ago

Publish a qualified installable build, then submit the completed 1.0.0 product to Apple.

Acceptance criteria:

  • Published Stacks version contains native model support; no local links in release lockfile.
  • Pantry immutable runtime and reusable CI pass.
  • bun run release:patch creates an installable qualification release.
  • App ID, App Store record, certificates and profile match com.stacksjs.launchpad.
  • All v1 native behavior passes on the signed sandboxed artifact.
  • Accurate icon, screenshots, privacy policy, support URL and review information.
  • Marketing version 1.0.0 and immutable numeric build number.
  • Apple upload accepted, build processed, review approved and app available.

Blocked by: launcher and saved-command qualification; Apple account requirements.

Reference: docs/planning/v1.md

6 days ago

Version 1.0.0 is on main. The first Store package (Build 11) passed application checks and signing but Apple validation rejected its embedded provisioning profile because the copied file retained mode 0600. The shared stx native signer now preserves the private source input and embeds a readable 0644 resource before signing. Fix: stacksjs/stx@746c97b, released as stx 0.2.718, currently in release CI. The next Store attempt will retain marketing version 1.0.0 with a new numeric build and use Buddy native publishing. The failed tag is unchanged. No Apple upload or review submission has completed yet.

6 days ago

Launchpad 1.0.0 (Build 12) was submitted through Buddy and is now WAITING_FOR_REVIEW, verified through both Apple's API and App Store Connect. Automatic release after approval is enabled. Public availability is still pending Apple approval.

  • Source on main: 7bab3f09bf974e455fa994020460685b8c1cce66.
  • Publish: ./buddy desktop:apple:publish --build-number 12.
  • Review submission: ./buddy desktop:apple:submit --build-number 12 --submit-for-review.
  • App checks: frozen installation, lint and typecheck passed; 12 tests and 62 assertions passed. Source CI: https://github.com/stacksjs/launchpad/actions/runs/40451856178.
  • Published dependencies include Buddy 0.75.326, stx/desktop 0.2.718 and Pantry 0.11.138; Craft uses the immutable 0.0.367 runtime source.
  • Apple accepted the rebuilt package. Its embedded profile is 0644, and the bundle contains no unreadable entries. No post-signing or app-specific permission workaround was used.
  • Six genuine native screenshots are attached, including Pantry and Clipboard History. Review notes disclose the external Pantry installer architecture.
  • The installed sandboxed qualification app is 1.0.0 (12); Command + Delete clears search and saved commands and appearance survive the upgrade.

Store package SHA-256: 1f67d2bc97662fc9a6a0993b410b01f1c252d0b5f1ad462a110bccafb05a518e.

Developer ID qualification notarization: 8d247bea-2b3d-4388-b938-cf7c3df07f4a, status Accepted. DMG SHA-256: 630161769181c0cb8977ae9a9644dc8052dab4bfe4ce1aafe465642997d63d43.

The failed original v1.0.0 tag and Build 11 remain unchanged. This issue stays open until Apple approves the app and it becomes publicly available.

6 days ago

Launchpad 1.0.1 Build 14 is public on GitHub and in Pantry's binary registry. The native GitHub workflow uses the Pantry action to sign, notarize, package, upload through the scanned registry API, and attach a credential-free publication receipt.

A dedicated service-account token is stored as the repository's PANTRY_TOKEN secret. Native publication is restricted to github.com/stacksjs/launchpad; a production request for another native package was rejected. The grant survived registry redeployment.

The first real installation exposed a generic Pantry materialization bug for app-only archives. The core correction is released in Pantry 0.11.140 and tracked in pantry-pm/pantry#252. A real install using the public 0.11.140 CLI completed successfully, followed by codesign verification, Gatekeeper acceptance as Notarized Developer ID, and stapler validation. The installed application is running from ~/Applications/Launchpad.app.

pantry upgrade
pantry install --user --kind app launchpad

The GitHub and Pantry archives have the same SHA-256: 832165e5a9186251864d27ed4b507d0965e333f41c83920cfa842eed981fb1ab. The registry receipt records a clean ClamAV scan and source revision 10aa57f.

App Store Connect accepted the 1.0.1 Build 14 upload. The submitted marketing version remains 1.0.0 Build 12, WAITING_FOR_REVIEW, with AFTER_APPROVAL release. Keep this issue open until Apple approves it and the app is actually available in the Mac App Store.

6 days ago

Verified the Pantry integration through the installed Launchpad 1.0.1 Build 14 UI after the user approved Keychain access. The saved connection restored without re-pairing and reported 121 installed packages before the test install.

  • All showed installed jq 1.8.1, zlib 1.3.2, and Inter 4.1 with their installed-version badges.
  • Keka was absent from All before installation and discoverable in the Pantry catalog as an uninstalled app.
  • Clicked Install with Pantry in Keka's package details. The UI progressed through running to Installed successfully, showed the actual Pantry output, disabled the Installed action, and offered Open application.
  • Keka 1.4.7 was installed into ~/Applications/Keka.app. The bundle passed codesign verification and Gatekeeper assessment as Notarized Developer ID.
  • Returning to All showed exactly one Keka result with Installed 1.4.7 and its original icon. Selecting that result opened the actual Keka application successfully.
  • Hidden Bar remained absent from All and discoverable in Pantry, confirming that uninstalled catalog entries stay out of All.

No application or framework code changes were needed. Buddy lint, typecheck, and all 12 application tests passed. Keka remains installed as the verified test application; its test-launched process was quit without changing preferences. The existing saved commands and appearance were preserved.

Sign in to comment on this issue.