-
-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Comparing changes
Open a pull request
base repository: Homebrew/brew
base: 4.6.8
head repository: Homebrew/brew
compare: 4.6.9
- 17 commits
- 9 files changed
- 5 contributors
Commits on Sep 1, 2025
-
Remove temporary audit exception for lsr
This removes the temporary `audit_download_strategy` exception for the `lsr` formula. This was necessary to be able to merge support for tangled.sh Git URLs, as it made the `using: :git` argument in the `lsr` formula redundant and caused the "formula audit" check to fail in brew CI.
Configuration menu - View commit details
-
Copy full SHA for 3eb57bc - Browse repository at this point
Copy the full SHA 3eb57bcView commit details
Commits on Sep 2, 2025
-
Configuration menu - View commit details
-
Copy full SHA for dc28719 - Browse repository at this point
Copy the full SHA dc28719View commit details -
Merge pull request #20621 from Homebrew/audit-container-deps
cask/audit: fix install of container deps
Configuration menu - View commit details
-
Copy full SHA for bfb0a55 - Browse repository at this point
Copy the full SHA bfb0a55View commit details -
Merge pull request #20615 from Homebrew/remove-lsr-special-case
Remove temporary audit exception for lsr
Configuration menu - View commit details
-
Copy full SHA for 75350b4 - Browse repository at this point
Copy the full SHA 75350b4View commit details -
SkipConditions: check disabled before deprecated
We have some formulae and casks that contain both `deprecate!` and `disable!` calls, presumably as a way of controlling the deprecation behavior before the disable date is reached. However, once the disable date has been reached, `Livecheck::SkipConditions` continues to skip the package as deprecated instead of disabled. This isn't a functional issue as the package is still skipped but it isn't accurate because it's not being skipped as disabled. This reorders `FORMULA_CHECKS` and `CASK_CHECKS` to run the disabled check before the deprecated check, so the disable date will take precedence when it's been reached.
Configuration menu - View commit details
-
Copy full SHA for 45a642c - Browse repository at this point
Copy the full SHA 45a642cView commit details -
Make
Pathname.prepend WriteMkpathExtensionas late as possible.Let's avoid weirdness in other parts of Homebrew by moving this prepend to be as late as possible.
Configuration menu - View commit details
-
Copy full SHA for e28fe44 - Browse repository at this point
Copy the full SHA e28fe44View commit details -
Merge pull request #20622 from Homebrew/livecheck/SkipConditions-chec…
…k-disabled-before-deprecated SkipConditions: check disabled before deprecated
Configuration menu - View commit details
-
Copy full SHA for 89f3c76 - Browse repository at this point
Copy the full SHA 89f3c76View commit details -
Merge pull request #20624 from Homebrew/later_pathname_prepend
Make `Pathname.prepend WriteMkpathExtension` as late as possible.
Configuration menu - View commit details
-
Copy full SHA for ab980dc - Browse repository at this point
Copy the full SHA ab980dcView commit details -
config: prioritize
::OS_VERSIONOn the [beta Bluefin LTS](https://docs.projectbluefin.io/lts), `brew config` reports: ```console OS: CentOS Stream release 10 (Coughlan) ``` This is due to the `/etc/redhat-release` file being prioritized over `::OS_VERSION` (`PRETTY_NAME` from `/etc/os-release`). On Bluefin LTS, `PRETTY_NAME` is `Bluefin LTS`. This commit reverses the order so `brew config` has better detection: ``` OS: Bluefin LTS ``` I tested on RHEL 10 and the OS line only changed in that the word "release" was omitted: ``` $ cat /etc/redhat-release Red Hat Enterprise Linux release 10.0 (Coughlan) $ grep PRETTY_NAME /etc/os-release PRETTY_NAME="Red Hat Enterprise Linux 10.0 (Coughlan)" ``` - This is an improvement on my previous PR #15788
Configuration menu - View commit details
-
Copy full SHA for ce8ae46 - Browse repository at this point
Copy the full SHA ce8ae46View commit details -
Configuration menu - View commit details
-
Copy full SHA for de8ff31 - Browse repository at this point
Copy the full SHA de8ff31View commit details
Commits on Sep 3, 2025
-
Merge pull request #20625 from osalbahr/config-prioritize-pretty-name
config: Remove use of `/etc/redhat-release`
Configuration menu - View commit details
-
Copy full SHA for 6c98d2b - Browse repository at this point
Copy the full SHA 6c98d2bView commit details -
livecheck: support trailing comments in watchlist
I ran `brew livecheck` today to check the packages in my watchlist and realized that it wasn't checking one package because I had added a trailing comment after the name (and `package # Comment` isn't a valid package name). I thought we had added support for trailing comments when we originally added comment support years back but I must have been mistaken. This adds support for trailing comments in livecheck watchlist files as part of refactoring the watchlist line parsing logic to only use one pass (instead of multiple `#map` and `#reject` calls). This maintains the existing behavior, where blank lines and lines starting with `#` are skipped, but does so in a more flexible manner. For example, the existing logic wouldn't skip a comment line that has one or more spaces before the `#` character but this new logic will correctly skip it.
Configuration menu - View commit details
-
Copy full SHA for 31cf8b4 - Browse repository at this point
Copy the full SHA 31cf8b4View commit details -
Merge pull request #20623 from Homebrew/livecheck/support-trailing-co…
…mments-in-watchlist livecheck: support trailing comments in watchlist
Configuration menu - View commit details
-
Copy full SHA for 4343324 - Browse repository at this point
Copy the full SHA 4343324View commit details -
Cask::Audit: fix
key not found: :latesterror`Cask::Audit.audit_livecheck_version` can raise a `key not found: :latest` error when a hash from livecheck's `latest_version` method doesn't have a `:latest` value. This error means that livecheck was unable to identify the latest upstream version but it can only be understood if the reader knows how this audit is implemented (and it may also depend on knowing the structure of livecheck's `latest_version` hash). Without that knowledge, the error doesn't make it clear which audit is failing and why. This addresses the issue by using `nil` as the default value for this `fetch` call and accounting for a `nil` `latest_version` value. This allows the audit to surface the usual "Version '1.2.3' differs from '' retrieved by livecheck" failure, which makes it more clear that livecheck isn't returning a version.
Configuration menu - View commit details
-
Copy full SHA for dce220e - Browse repository at this point
Copy the full SHA dce220eView commit details -
Configuration menu - View commit details
-
Copy full SHA for f23b848 - Browse repository at this point
Copy the full SHA f23b848View commit details -
Merge pull request #20629 from Homebrew/cask/audit-fix-key-not-found-…
…error Cask::Audit: fix `key not found: :latest` error
Configuration menu - View commit details
-
Copy full SHA for bd57ad8 - Browse repository at this point
Copy the full SHA bd57ad8View commit details -
Merge pull request #20630 from Homebrew/pid_path-libSystem
utils/pid_path: use libSystem
Configuration menu - View commit details
-
Copy full SHA for 1c959c2 - Browse repository at this point
Copy the full SHA 1c959c2View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 4.6.8...4.6.9