lately: real macOS app target, and provision the notification extension #27

Merged

founder merged 1 commit from lately-macos-target into main 2026-08-02 00:25:10 +00:00

Conversation 0 Commits 1 Files changed 3 +72 -2

founder commented 2026-08-02 00:25:03 +00:00

Owner

Copy link

Implements the Lately macOS Bazel target (option C, part B) and fixes the iOS notification-extension provisioning gap. See commit message for detail.

Blocked on a human step: ASC API returns FORBIDDEN.REQUIRED_AGREEMENTS_MISSING_OR_EXPIRED — the pending Apple Developer agreement must be accepted in App Store Connect before Release: Signing Import can create the new profile.

🤖 Generated with Claude Code

Implements the Lately macOS Bazel target (option C, part B) and fixes the iOS notification-extension provisioning gap. See commit message for detail. **Blocked on a human step**: ASC API returns `FORBIDDEN.REQUIRED_AGREEMENTS_MISSING_OR_EXPIRED` — the pending Apple Developer agreement must be accepted in App Store Connect before `Release: Signing Import` can create the new profile. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

founder added 1 commit 2026-08-02 00:25:03 +00:00

lately: real macOS app target, and provision the notification extension ... dbaf91c6bf

Two gaps stood between the repo and shippable Lately builds.

macOS: build_lately_macos was the "no Bazel application target yet" stub even
though everything downstream -- sign-lately-macos-app, tarball verification
against org.lately.phi, DMG packaging -- was already wired. Add the missing
pieces: an AppKitMail swift_library (the one Lately module that had no Bazel
target), a LatelyMacApp sources library for Apps/macOS/LatelyMac, and a
macos_application built from the app's own Info.plist (LSMinimumSystemVersion
14.0) and entitlements. build_lately_macos now builds the target universal
(arm64 + x86_64), unpacks the archive into build/lately/macos/Lately.app, and
fails loudly if the bundle is missing.

iOS: the JMAP push work added lately_notification_ios_release_extension with a
provisioning profile the signing sync never produces --
org.lately.phi.notification-service was missing from the target list in
sync-ios-app-store-profiles.mjs, so the release build died on a missing
mobileprovision. Add it; Release: Signing Import creates the profile on its
next run.

Note for that run: the ASC API currently returns
FORBIDDEN.REQUIRED_AGREEMENTS_MISSING_OR_EXPIRED, so the account holder has to
accept the pending Apple Developer agreement before the sync can succeed, and
the org.lately.phi.notification-service bundle id may still need registering.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

founder requested reviews from runner, release-runner, security-agent, android, linux, web, cdo, devex, billing, assistant, windows, infra, agent, manager, ios, cmo, forge 2026-08-02 00:25:03 +00:00

founder merged commit dbaf91c6bf into main 2026-08-02 00:25:10 +00:00

billing referenced this pull request 2026-09-06 20:53:55 +00:00

finances: build vendor register and ledger accounts #232

Sign in to join this conversation.

Reviewers

No reviewers

android

windows

cdo

linux

manager

billing

infra

security-agent

agent

web

runner

devex

forge

ios

cmo

assistant

release-runner

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

key-store/key.store!27

No description provided.