Skip to content

docs(infrastructure): note Homebrew 6 tap-trust on the macOS Tahoe 26.5 stack#4

Draft
arcappcircle wants to merge 1 commit into
developfrom
docs/tahoe26.5-homebrew6-note
Draft

docs(infrastructure): note Homebrew 6 tap-trust on the macOS Tahoe 26.5 stack#4
arcappcircle wants to merge 1 commit into
developfrom
docs/tahoe26.5-homebrew6-note

Conversation

@arcappcircle

@arcappcircle arcappcircle commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

What

Adds a caution note under the macOS build-environment toolset table in infrastructure/ios-build-infrastructure.md covering the upcoming macOS Tahoe 26.5.1 stack's Homebrew change.

Why

The 26.5 stack ships Homebrew 6.x (up from 5.1.0 on Tahoe 26.3.2). Homebrew 6.0 introduced a tap-trust security mechanism: brew refuses to install formulae from untrusted third-party taps until the tap is trusted. Customers who brew install from a third-party tap in a custom script will hit an error without brew trust first. The note documents the workaround and also flags the Node default (stays 22, 24 available).

Notes / placement

  • I did not add a full macOS Tahoe 26.5.1 column to the toolset table yet - most per-tool versions resolve at image build time and aren't validated until the CI build of the stack completes. The column should be added with real values once PL-194 builds and smoke-tests pass.
  • Merge timing: this references an upcoming stack - hold until the 26.5 stack goes live, or merge now as forward-looking docs (reviewer's call).

Ready-to-paste release-notes.md bullet for the release that ships the stack:

The new macOS Tahoe 26.5 runner stack upgrades Homebrew to 6.x. Homebrew 6 requires third-party taps to be explicitly trusted (brew trust) before installing their formulae in custom scripts. The default Node version remains 22, with Node 24 available via the Install Node step. InfrastructureBadge CloudBadge

Companion to ac-script-agent #71/#72 (tahoe26.5 toolset) and ac-agent-build #52 (android runner sync).

Migrated from appcircle-docusaurus#1238.


Created on behalf of ozcan@appcircle.io via Arc.

Summary by CodeRabbit

  • Documentation
    • Added an important caution for the iOS build environment on macOS Tahoe 26.5.1.
    • Clarified that this stack uses Homebrew 6.x, which may require trusted taps before installing packages from third-party sources.
    • Included the recommended commands to trust a tap and continue installation.
    • Noted that Node 22 is still the default, with 24 available through the standard install step.

@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

This change adds a documentation caution callout to the iOS build infrastructure guide, describing Homebrew 6.x behavior on the macOS Tahoe 26.5.1 stack, required brew trust steps for untrusted taps, and a note about Node 22 default availability with Node 24 as an option.

Changes

Documentation update

Layer / File(s) Summary
Homebrew trust caution block
docs/infrastructure/ios-build-infrastructure.md
Adds a caution callout describing Homebrew 6.x blocking untrusted third-party taps on macOS Tahoe 26.5.1, with brew trust/brew install guidance and a note on Node 22 default vs Node 24 availability.

Related PRs: None identified.

Suggested labels: documentation

Suggested reviewers: None identified.

Poem

A caution box, so neat and small,
Warns of taps that Brew won't call,
Trust them first, then install with cheer,
Node twenty-two still lives right here,
Hop along, the docs are clear! 🐇📘

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the docs change about Homebrew 6 tap-trust guidance for the macOS Tahoe 26.5 stack.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/tahoe26.5-homebrew6-note
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch docs/tahoe26.5-homebrew6-note

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/infrastructure/ios-build-infrastructure.md`:
- Around line 132-143: Update the caution heading in the iOS build
infrastructure docs so it matches the stack version used in the body text and
tables. The issue is the heading references Tahoe 26.5 while the content refers
to 26.5.1; make the version consistent throughout that caution block so readers
can identify the correct macOS stack.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e55c04d6-c4eb-4da0-905b-0a3e74bd9158

📥 Commits

Reviewing files that changed from the base of the PR and between 9d9a9eb and b5ce3d5.

📒 Files selected for processing (1)
  • docs/infrastructure/ios-build-infrastructure.md

Comment on lines +132 to +143
:::caution Homebrew 6 on the macOS Tahoe `26.5` stack

The upcoming macOS **Tahoe `26.5.1`** stack ships **Homebrew 6.x** (up from `5.1.0` on the Tahoe `26.3.2` stack). Starting with Homebrew `6.0`, `brew` no longer installs formulae from **untrusted third-party taps** until the tap is explicitly trusted. If a [custom script](/workflows/common-workflow-steps/custom-script) step installs from a third-party tap, add a trust step first:

```bash
brew trust <user>/<tap>
brew install <user>/<tap>/<formula>
```

Formulae from the default Homebrew taps are not affected. Node also changes on this stack: the default stays **Node 22**, with **Node 24** available via the [Install Node](/workflows/react-native-specific-workflow-steps/node-install) step.

:::

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Align the caution heading with the target stack version.

The block title says 26.5, but the surrounding text and tables refer to 26.5.1. Please make the version consistent so readers don’t infer the warning applies to the wrong image.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/infrastructure/ios-build-infrastructure.md` around lines 132 - 143,
Update the caution heading in the iOS build infrastructure docs so it matches
the stack version used in the body text and tables. The issue is the heading
references Tahoe 26.5 while the content refers to 26.5.1; make the version
consistent throughout that caution block so readers can identify the correct
macOS stack.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
appcircle-docs b5ce3d5 Commit Preview URL

Branch Preview URL
Jul 07 2026, 12:00 PM

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
appcircle-docs b5ce3d5 Commit Preview URL

Branch Preview URL
Jul 07 2026, 12:01 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants