ci: pin Homebrew version in CI runs#51543
Conversation
There was a problem hiding this comment.
Hello @nmggithub! It looks like this pull request touches one of our dependency or CI files, and per our contribution policy we do not accept these types of changes in PRs.
To move this PR forward, please:
- Revert the dependency/CI file changes from your branch. (e.g.
yarn.lock,.yarn/,.yarnrc.yml,.github/workflows/,.github/actions/) - Ensure your branch allows maintainer commits so a maintainer can push the necessary dependency changes on your behalf.
- Leave a comment letting reviewers know the dependency change is still needed.
For maintainers
To land this PR, push a verified commit to the contributor's branch with the required dependency/CI changes, then dismiss this review.
|
No Release Notes |
|
I was unable to backport this PR to "40-x-y" cleanly; |
|
I have automatically backported this PR to "42-x-y", please check out #51545 |
|
I have automatically backported this PR to "43-x-y", please check out #51546 |
|
I have automatically backported this PR to "41-x-y", please check out #51547 |
|
@nmggithub has manually backported this PR to "40-x-y", please check out #51555 |
ci: pin Homebrew version in CI runs (#51543) * feat: pin Homebrew version in CI runs * feat: validate Homebrew asset before installing * fix: fix sha256 verificaton * fix: inline sha256 check * fix: remove GitHub CLI integrity check
Description of Change
We had a recent macOS build that failed in CI due to a bug in Homebrew: https://github.com/electron/electron/actions/runs/25497330347
This appears to be fixed in a newer version of Homebrew (5.1.10) via this commit: Homebrew/brew@1c8cbf3 (Homebrew/brew#22137)
However, it seems we currently just use whatever version of Homebrew is on our runners. For better control, we might be better served pinning the Homebrew version ourselves and installing it via their published
.pkgfiles.Checklist
Release Notes
Notes: none.