TL;DR: Homebrew 6.0.0 shipped on June 11, 2026, with four headline changes: a new tap trust security mechanism, Linux Bubblewrap sandboxing enabled by default, the internal JSON API promoted to default, and initial macOS 27 (Golden Gate) support. Intel x86_64 macOS support is being phased out by September 2027.

What Changed in Homebrew 6.0.0

Homebrew maintainer Mike McQuaid announced Homebrew 6.0.0 on June 11, 2026, describing it as the most significant release since 5.0. The changes reflect two converging priorities: hardening the package manager against supply-chain attacks that have plagued other ecosystems, and expanding Homebrew's reach as a "package manager for everywhere" — macOS, Linux, WSL, and now Windows via winget.

6.0.0major version released June 11, 2026
~30%faster brew leaves command
Sept 2026Intel macOS drops to Tier 3 (no CI, no bottles)
Sept 2027Intel macOS support fully removed

1. Tap Trust: Closing a Supply-Chain Gap

The most security-significant change is the new tap trust mechanism. Previously, running brew tap <third-party-repo> would add the repository and allow its Ruby formula scripts to execute without any explicit trust gate. In 6.0.0, taps must be explicitly trusted before they can install packages.

The Homebrew team has published new Supply Chain Security documentation alongside this release, detailing both existing protections (macOS sandboxing, human review on all changes, environment filtering) and new ones (Linux sandboxing, blocking access to sensitive filesystem locations, additional scrutiny for taps sourcing from higher-risk ecosystems).

💡
Update Your CI/CD Workflows
If you use third-party taps in automated pipelines, you'll need to add explicit brew trust steps or use the new brew tap --force-auto-update alternatives. Brewfile users can also express trust inline. Check the release notes for the exact syntax before updating in production.

2. Linux Bubblewrap Sandboxing — Now Default

Until this release, Linux users ran Homebrew's build, test, and postinstall phases without any sandboxing. Homebrew 6.0.0 enables Linux Bubblewrap sandboxing by default, achieving parity with macOS where these phases have been sandboxed for years.

Key details:

  • Build, test, and postinstall phases now run in isolated Bubblewrap containers on Linux
  • Homebrew's macOS and Linux sandbox logic has been unified into shared code
  • Bubblewrap is automatically installed on hosted Ubuntu CI environments
  • Syntax-only jobs skip sandbox setup to avoid unnecessary overhead

3. Internal JSON API Becomes the Default

The internal JSON API, opt-in since Homebrew 5.0.0 via HOMEBREW_USE_INTERNAL_API, is now the default in 6.0.0. The old variable is deprecated and should be removed from your environment.

This API consolidates all Homebrew metadata into a single download, with cascading performance benefits:

  • brew update completes faster with fewer network requests
  • brew leaves is approximately 30% faster
  • brew upgrade parallelizes bottle tab fetching
  • Startup time improved through better Ruby library loading
ℹ️
Remove the Old Env Variable
If you have HOMEBREW_USE_INTERNAL_API=1 set in your shell profile, CI environment, or .env files, remove it. The variable is now deprecated and may cause warnings or unexpected behavior in future releases.

4. macOS 27 (Golden Gate) Support — and the Intel Sunset

Homebrew 6.0.0 adds initial support for macOS 27 (Golden Gate), Apple's upcoming OS release. Crucially, macOS 27 drops Intel processor support entirely — and Homebrew is following suit with a published deprecation timeline.

Date Intel x86_64 macOS Status
September 2026 Moves to Tier 3 — no CI support, no new binary bottles
September 2027 Fully unsupported — all related code deleted from the project

M5 and M5 Pro/Max CPU detection is also included in this release.

5. brew bundle Gets a Major Upgrade

brew bundle — Homebrew's declarative Brewfile system — gains several significant improvements:

  • Parallel job execution for faster installs
  • npm package support (JavaScript ecosystem)
  • krew plugin support (kubectl plugins)
  • winget package support (Windows-only, WSL environments)
  • Wider platform coverage across formulae and casks

This brings Homebrew closer to being a truly universal development environment setup tool, capable of managing your entire dependency stack across package managers in a single Brewfile.

💡
Homebrew Is Now Recommended on Windows
Microsoft has added Homebrew to its official Windows Developer Config recommendation for WSL environments. Combined with the new winget support in brew bundle, Windows developers using WSL can now manage their full stack through Homebrew.

Key Takeaways

  • Tap trust mechanism introduced — third-party taps require explicit trust before installing
  • Linux Bubblewrap sandboxing enabled by default — matches macOS isolation guarantees
  • Internal JSON API is now the default — remove HOMEBREW_USE_INTERNAL_API if set
  • macOS 27 (Golden Gate) initial support added; Intel Mac loses binary builds Sept 2026, fully dropped Sept 2027
  • brew bundle now supports npm, krew, and winget (Windows) packages
  • ~30% faster brew leaves, parallel bottle fetching on upgrades

How to Upgrade

brew update
brew upgrade
brew --version  # Should show Homebrew 6.0.0

If you use third-party taps, review the new tap trust workflow in the release notes. Remove any HOMEBREW_USE_INTERNAL_API entries from your shell config. Apple Silicon users and macOS 27 beta testers should see immediate benefits; Intel Mac users have until September 2026 before binary package support is cut.

🔗
Resources · Official Sources · Getting Started
— Homebrew 6.0.0 Official Release Notes (GitHub)
— Homebrew Official Repository (GitHub) — installation scripts and source code
— homebrew-bundle (GitHub) — Brewfile declarative package management