Skip to content

docs: clarify universal Homebrew cask - #1628

Merged
steipete merged 1 commit into
mainfrom
fix/issue-1193-homebrew-docs
Jun 19, 2026
Merged

docs: clarify universal Homebrew cask#1628
steipete merged 1 commit into
mainfrom
fix/issue-1193-homebrew-docs

Conversation

@steipete

@steipete steipete commented Jun 18, 2026

Copy link
Copy Markdown
Owner

Closes #1193

Summary

  • Describe the official Homebrew cask as universal on Intel and Apple silicon.
  • Update the English website fallback and all 21 localized setup messages.
  • Remove the stale arm64-only instruction from the Homebrew release playbook.
  • Add changelog credit for the original Intel support report.

Proof

  • Exact candidate: df7a9fa0969027795e048211f501a829cee49c0b.
  • Current official cask downloads the universal macOS zip and has no architecture restriction.
  • make check passes on the exact head: all 21 site locales, format, and strict lint clean.
  • make docs-list passes on the exact head.
  • Exact-head Codex autoreview clean, confidence 0.87.
  • Existing-profile Chrome visual smoke for English, German, and RTL Arabic remains exact: feature bytes match stable patch ID 644da519, with no clipping or layout change.

@clawsweeper

clawsweeper Bot commented Jun 18, 2026

Copy link
Copy Markdown

Codex review: needs maintainer review before merge. Reviewed June 19, 2026, 4:36 AM ET / 08:36 UTC.

Summary
This PR updates website install copy, localized setup messages, the Homebrew release playbook, and changelog text to describe the official Homebrew cask as universal on Intel and Apple silicon.

Reproducibility: not applicable. as a runtime bug; source inspection shows current main still describes Homebrew as Apple Silicon-only while the current cask metadata and PR head describe the cask as universal.

Review metrics: 2 noteworthy metrics.

  • Docs Surface: 4 files changed, +47/-46. The diff is limited to docs, website copy, localized setup strings, and changelog text.
  • Localized Install Copy: 21 locales, 2 message keys each. The locale-wide copy change makes placeholder preservation and layout proof relevant before merge.

Root-cause cluster
Relationship: fixed_by_candidate
Canonical: #1193
Summary: This PR is the candidate docs fix for the linked Intel Mac/Homebrew support issue; older Homebrew docs and Intel-support items provide context but do not supersede this PR.

Members:

  • canonical: Support for Intel Mac #1193 - The PR body uses closing syntax for this issue, and GitHub reports this PR as its closed-by reference.
  • partial_overlap: Update Homebrew cask install command #1189 - That merged PR updated the README Homebrew cask command but not the website, locale, or release-playbook architecture wording changed here.
  • partial_overlap: Remove Intel support claims on website #650 - That closed unmerged PR discussed earlier Intel/Homebrew website wording, but it was superseded by later cask metadata and this narrower correction.
  • partial_overlap: QoL: brew distribution for Intel Mac #300 - That closed issue covered Intel Mac Homebrew distribution policy; this PR is narrower and updates docs now that the official cask metadata is universal-capable.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Merge readiness
Overall: 🦞 diamond lobster
Proof: 🦞 diamond lobster
Patch quality: 🦞 diamond lobster
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Risk before merge

  • [P1] At review time, GitHub still showed one exact-head macOS test shard queued, so normal branch protection should verify required checks before merge.

Maintainer options:

  1. Decide the mitigation before merge
    Land the scoped docs update once exact-head required checks finish and owner review confirms the public Homebrew cask policy.
  2. Pause or close
    Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge

  • [P2] Owner-authored docs PR should stay in maintainer merge/check handling; there is no narrow code repair for automation.

Security
Cleared: No security or supply-chain-sensitive code paths are changed; the diff is limited to docs, website copy, locale strings, and changelog text.

Review details

Best possible solution:

Land the scoped docs update once exact-head required checks finish and owner review confirms the public Homebrew cask policy.

Do we have a high-confidence way to reproduce the issue?

Not applicable as a runtime bug; source inspection shows current main still describes Homebrew as Apple Silicon-only while the current cask metadata and PR head describe the cask as universal.

Is this the best way to solve the issue?

Yes; the PR is the narrow maintainable fix because packaging and cask metadata already match, so only docs, site copy, locale strings, and release playbook wording need to change.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 99cd674ba08e.

Label changes

Label justifications:

  • P3: This is a low-risk installation documentation clarification with no app runtime behavior change.
  • rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor proof gate does not apply because this is an owner-authored docs/changelog PR, though the body and owner comment include exact-head checks and visual-smoke notes.
Evidence reviewed

What I checked:

  • Repository policy read: AGENTS.md was read fully, and its docs/release guidance shaped the read-only review path. (AGENTS.md:1, 99cd674ba08e)
  • Current main has stale website copy: Current main still says GitHub Releases are universal while Homebrew is Apple Silicon-only. (docs/index.html:166, 99cd674ba08e)
  • Current main has stale release playbook guidance: Current main still tells releasers to keep an arm64 cask restriction while using the universal app zip URL. (docs/releasing-homebrew.md:30, 99cd674ba08e)
  • PR head corrects the docs wording: The PR changes the public install copy to say GitHub Releases and Homebrew are both universal, and removes the Apple Silicon-only Homebrew phrase. (docs/index.html:166, df7a9fa09690)
  • PR head corrects Homebrew playbook guidance: The PR changes the manual cask step to keep only the macOS Sonoma minimum and explicitly not add an architecture restriction because the app zip is universal. (docs/releasing-homebrew.md:30, df7a9fa09690)
  • External cask metadata matches the PR direction: The current cask downloads CodexBar-macos-universal v0.36.1, depends on macOS Sonoma, and has no architecture restriction. (steipete/homebrew-tap/Casks/codexbar.rb:5)

Likely related people:

  • steipete: Current-main blame ties the stale website, locale, and Homebrew release-playbook wording to his v0.36.1 docs update, and the PR head is also authored by him. (role: current docs/release area contributor; confidence: high; commits: 06fea2c897cc, df7a9fa09690, cbefd7daff8b; files: docs/index.html, docs/site-locales.mjs, docs/releasing-homebrew.md)
  • Alexander Botkin: The earlier macOS install-architecture docs clarification was co-authored by Alexander Botkin and touched the same website support wording area. (role: install-architecture docs co-author; confidence: medium; commits: cbefd7daff8b; files: docs/index.html)
  • Yuxin Qiao: Recent static musl release-artifact work touched the Homebrew release playbook and adjacent release documentation paths. (role: recent adjacent release-doc contributor; confidence: medium; commits: ae08d86d04cc; files: docs/releasing-homebrew.md, docs/RELEASING.md, .github/workflows/release-cli.yml)
  • SSakutaro: The merged Homebrew cask command update changed adjacent install documentation and changelog context for the same distribution surface. (role: adjacent Homebrew install-doc contributor; confidence: medium; commits: 113719232dd3; files: README.md, CHANGELOG.md)
What the crustacean ranks mean
  • 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
  • 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
  • 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
  • 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
  • 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
  • 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
  • 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works
  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@clawsweeper clawsweeper Bot added rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. labels Jun 18, 2026
@steipete
steipete force-pushed the fix/issue-1193-homebrew-docs branch from 58630ab to 3047ab1 Compare June 18, 2026 15:29
@steipete

Copy link
Copy Markdown
Owner Author

Final rebase proof for exact head 3047ab11:

  • conflict was changelog-only; current musl release documentation auto-merged with the universal-cask correction
  • all 21 website locales / 50 messages validate
  • docs inventory and diff checks pass
  • prior autoreview clean (0.92)
  • website content/layout diff is unchanged from reviewed existing-Chrome visual smoke in English, German, and Arabic RTL; no clipping or layout regression observed
  • current official cask proof remains v0.36.1 universal app archive, macOS Sonoma minimum, no architecture restriction
  • public model identifier gate: N/A; docs-only install change

Exact-head CI restarted.

@steipete
steipete force-pushed the fix/issue-1193-homebrew-docs branch 3 times, most recently from 56ab742 to 3954d1e Compare June 18, 2026 21:28
@steipete
steipete force-pushed the fix/issue-1193-homebrew-docs branch from 3954d1e to df7a9fa Compare June 19, 2026 07:08
@steipete
steipete merged commit 6c5aa41 into main Jun 19, 2026
27 of 33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support for Intel Mac

1 participant