feat: macOS distribution follow-ups: homebrew-core submission and a stapled offline-safe container

Open
#120 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
macos
Domain
release

Research direction

This is a tracker whose items are gated on external triggers, not code changes. Read the requirement lines BREW-07 and DIST-06 in .planning/milestones/v0.5.0-REQUIREMENTS.md (lines 59-60, 66-67) and the Later section of .planning/ROADMAP.md. Nothing is startable until adoption or offline first-launch evidence exists, so done means the trigger evidence is linked in this issue.

Written by the indexing model from the issue text.

Description

area:ci feature priority:low spec-needed
What problem does this solve?
  • Users must brew tap seanb4t/tap before installing.
  • First launch on macOS needs the network for the Gatekeeper check, because a bare Mach-O or a .zip cannot carry a stapled notarization ticket.
What should it do?
  • BREW-07: submit to homebrew-core once adoption meets its notability criteria.
  • DIST-06: ship a stapled .pkg or .dmg if evidence shows users hitting the offline first-launch case.
Which surface does this affect?

Release, signing, or supply chain

Is this covered by an existing command or tool today?

The tap cask and notarized, unstapled assets (v0.5.0).

Acceptance criteria
  • Each item started only when its trigger is met; the trigger evidence is linked here.

Source (GSD planning files, archived at d384473e): .planning/milestones/v0.5.0-REQUIREMENTS.md:59-60,66-67; .planning/ROADMAP.md (Later)


🤖 Generated with Claude Code

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

Dominant language
Go
Stars
0
Forks
0
Avg merge
5h 16m
Merged PRs (30d)
107

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seanb4t/codegraph-go

All issues in seanb4t/codegraph-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.