@p There were at least three medium-to-large sized instances that pulled the buggy revision (which stayed up for a least two weeks before the fix), so I wouldn't call the spread exactly low, but most are running releases anyway so I guess it's good that it got caught before the next one.