-
Notifications
You must be signed in to change notification settings - Fork 161
Update GHA for mac. #704
Comments
I think we should just run with |
The downside of that is that that then our CI breaks whenever Personally, I'm not very keen on that type of setup, since I fear Murphy's law, i.e. it'll break when we need to merge something urgently, but don't have the time to fix CI for a new OS. (We'd have time a few weeks later or before, just not right then.) I seem to remember that for a certain period of time for Ubuntu OTOH, it would prevent us form running 2 major versions behind. |
Things should not break if I would not worry however that it would become a blocker. If this happens we can always quickly downgrade the CI on order to still have passing checks. In addition, that is a special case anyway that needs special attention anyway. My personal strategy is to only hardcode when needed, not to hardcode when possibly useful. But, whatever you want ;). |
Don't have a strong opinion but have similar experiences with some other projects. Especially (if/) when rely on some of the stuff "custom sauce or updates" that GitHub and/or Azure actions runners are shipped with. |
We're getting the following warning from GHA:
We'll likely need to slightly modernize our CI for mac.
The text was updated successfully, but these errors were encountered: