Brewfile cleanup compatibility across Homebrew formula rename transitions

Homebrew's brew bundle command manages packages declaratively through a Brewfile, but upstream repositories occasionally rename formulae. When a Brewfile references an old name, the cleanup option may attempt to remove software that no longer matches the current formula identifier, while installation may fail to recognize the renamed package. This creates a compatibility boundary between archived Brewfiles and evolving tap repositories. The exact behavior depends on whether Homebrew core treats renamed formulae as aliases, missing entries, or distinct packages during dependency resolution. Users relying on reproducible environments need clarity on how cleanup interacts with these renames before committing to a long-lived Brewfile strategy.

Does brew bundle treat a renamed formula as an alias of the new name during cleanup, or does it remove the old package and install the new one separately? How does dependency resolution handle a Brewfile that references a formula name deprecated in a recent Homebrew version? Is there a documented compatibility window for Brewfiles generated after upstream renames?