Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cask upgrade drops third-party tap name and selects unrelated disabled cask

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

Maintainers usually reply within 1 day

@noah-qin is already working on this.

Since Oct 25, 2026.

  • #293 by @noah-qin — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
cli, desktop

Research direction

The report identifies upgrade command construction as the suspected source but names no files or tests. Start by tracing how BrewUI gets an installed cask’s identity and builds the brew upgrade --cask command. Reproduce with stablyai/orca/orca; done when the generated command retains that tap-qualified name and upgrades the intended cask.

Written by the indexing model from the issue text.

Description

Before submitting
  • I have searched the issues and pull requests for duplicates.
  • I am reporting a specific problem with BrewUI and have described how to reproduce it, or the circumstances of an intermittent failure.
What happened?

When upgrading Orca from the Homebrew GUI, the app generates:

brew upgrade --cask orca

This resolves to the unrelated Plotly Orca cask in homebrew/cask and fails with:

Not upgrading orca, it is disabled because it does not pass the macOS Gatekeeper check!
It was disabled on 2026-09-01.

The intended app is Orca from stablyai/orca/orca.

Expected behaviour

Preserve the installed cask’s source tap and generate:

brew upgrade --cask stablyai/orca/orca
Steps to reproduce
  1. Install Orca using brew install --cask stablyai/orca/orca.
  2. Attempt to upgrade Orca through the Homebrew GUI.
  3. Observe that the generated command uses orca without its tap.
App version and build

0.6.0 (1201)

How was the app installed?

Homebrew cask

macOS version and build

Version 27.0 (26A428)

Mac processor

Apple silicon

Homebrew configuration
Homebrew
HOMEBREW_VERSION: 7.0.9
ORIGIN: https://github.com/Homebrew/brew
HEAD: cdc1ca503231b9a96da64526774915d913c3ec9f
Last commit: 10 days ago
Branch: stable
HOMEBREW_PREFIX: /opt/homebrew
Homebrew Ruby: 4.0.7 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/4.0.7/bin/ruby

System
Core tap: N/A
Core cask tap: N/A
CPU: deca-core 64-bit arm_firestorm_icestorm
Clang: 21.0.0 build 2100
Git: 2.54.0 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 27.0-arm64
CLT: 27.0.0.0.1788430756
Xcode: 27.0
Metal Toolchain: N/A
Rosetta 2: false

Environment (HOMEBREW_*)
HOMEBREW_VERSION: 7.0.9
HOMEBREW_PREFIX: /opt/homebrew
Logs, screenshots and crash reports

No response

Additional context

Verified potentially conflictinghomebrew/cask/orca was not installed. Using the command line brew upgrade --cask stablyai/orca/orca in terminal succeeds.

The suspected cause is loss of the tap-qualified identity when constructing the upgrade command in BrewUI.

Dominant language
Swift
Stars
2.7k
Forks
87
Avg merge
2d 13h
Merged PRs (30d)
11

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 Homebrew/BrewUI

All issues in Homebrew/BrewUI

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.