Homebrew Cask bottle naming limits: no timezone encoding

Homebrew Cask formulae define package metadata, dependencies, and installation steps in Ruby. The version directive supports explicit pinning, but the bottle naming convention uses only platform identifiers and version numbers. No timezone component appears in the filenames, so the download and extraction process is independent of the host’s regional settings.

When a user runs brew install in different time zones, log entries show timestamps adjusted to the local zone, yet the underlying package chosen remains the same. This suggests that installation logic does not incorporate date conversion, but the displayed logs do. The behavior is documented, yet there is no explicit statement confirming that timezone variations cannot affect bottle selection or caching.

Key uncertainty: does the absence of timezone data in bottle names guarantee deterministic behavior across all locales, or could locale‑dependent filename sorting influence the brew leaves output and potentially lead to non‑deterministic install paths?

Questions:

• Is there any scenario where Homebrew Cask could select a different bottle based on the system’s timezone?
• Could locale settings alter the order of bottles in brew leaves and affect deterministic installs?
• Does the Homebrew team plan to document explicit timezone independence for bottle naming in future releases?