Hello, This is the first (and, perhaps, last[1]) monthly update on GitLab CI. This month in particular deserves its own little email for the following reasons: 1. Some of the Darwin runners recently spontaneously self-upgraded, introducing toolchain changes that broke CI. All the fixes are now on GHC's master branch. This leaves us with two choices: A) Re-enable the affected runners now. All current patches will have a 50% of failing CI because the old problems are still present. Users (you) can rebase your patches to avoid this problem. B) Wait before re-enabling the runners. All in-flight MRs have a better chance of getting green CI and/or organically getting rebased for other reasons. However, Darwin capacity would remain at 50% for longer, slowing down all pipelines. My current plan is to wait one week before re-enabling the runners, but ultimately it's not my call. Opinions welcome. 2. I will be on vacation from July 17 to July 28 (weeks 29 and 30). Please tell Marge to be good while I am away. 3. GitLab was recently upgraded. Please do not be alarmed by any UI changes. Enjoy! -Bryan [1]: Intuitively, I like the idea of giving monthly updates about GitLab CI. But I don't know if it will be practical or valuable. I'll take a look in a month to see if there's anything notable to write about again.