Reset .fork-sync-state to v11.3.0 (last-synced upstream tag) and remove the release-tail step that overwrote it with the fork release tag, which would stall upstream-sync. Update SESSION-STATE/TODO/CICD-STATUS/README for the live signed+notarized v100.1.0 release.
2.8 KiB
2.8 KiB
TODO — CommandTabFree
Updated 2026-06-16. The signed + notarized publishing pipeline is LIVE — v100.1.0 is released (Gatekeeper-accepted). Remaining items are auto-update, the Homebrew cask, and upstream-sync. Full detail: docs/CICD-STATUS.md, docs/EXECUTION-STATUS.md §3.
✅ Signed + notarized releases — DONE (2026-06-16)
- Apple Developer ID
Developer ID Application: James Maes (2X834TJ5MA)provisioned; cert + app-specific password inproductionsecrets (APPLE_P12_CERTIFICATE/APPLE_P12_PASSWORD/APPLE_ID/APPLE_PASSWORD/APPLE_TEAM_ID). CODE_SIGN_IDENTITY+ Manual style +TEAM_IDset inconfig/local.xcconfig.- Vendored
vendor/Sparkle/Helpers/*committed re-signed under the fork Developer ID. - Full release tail proven on CI (run
27643432063): signed → notarized → stapled → released. v100.1.0 published.
Auto-update (deferred by choice — appcast already publishes to gh-pages)
- Real
DOMAIN— replacefork.invalidinconfig/local.xcconfigwith the fork host (kof22.com). - Serve the gh-pages
appcast.xmlathttps://<DOMAIN>/appcast.xml(CNAME the gh-pages site). git rmthe in-treeappcast.xmlskeleton + gitignore it (feed is published out-of-tree to gh-pages); flipSUEnableAutomaticChecksback on (PLAN §3.2).
Homebrew cask (now that builds are notarized)
- Drop the quarantine-strip postflight (
xattr) fromKofTwentyTwo/homebrew-tapCasks/commandtabfree.rb— no longer needed for a notarized app. - Bump the cask to v100.1.0.
Upstream-sync automation
.fork-sync-statereset tov11.3.0; release tail no longer clobbers the cursor with the fork tag (ci_cd.yml).- Re-wire the cursor advance into the upstream-sync merge flow so it records the synced UPSTREAM tag (not the fork release tag) —
upstream_sync.yml(PLAN §4.2). SYNC_BOT_TOKEN— GitHub App installation token (or fork PAT with contents + pull-requests write). DefaultGITHUB_TOKENdoes NOT re-trigger PR checks, so guards never run on the sync PR.- External cron — hit
repository_dispatch(typeupstream-sync) from an external scheduler (immune to GitHub's 60-day in-reposchedule:auto-disable). - Sync PR labels
sync/conflict/chokepoint-refreshcreated.
Bootstrap acceptance tests (after the above)
- Sync PR through the bot shows guard checks running.
- A deliberately-relocked branch goes RED on
guard.yml. - Fork build N→N+1 auto-updates via Sparkle (needs DOMAIN/appcast live).
Done earlier this session (2026-06-16)
- genstrings consistency gate fixed — regenerated base
Localizable.stringsfrom source (d1e1b296). build_app.shbuilds ad-hoc until cert provisioned; was failing on upstream's Developer ID (6070f0cb). Push CI green (run27634828800).