Not only is it a bad idea, it's actively breaking things as @main currently points to the soon-to-be-released-but-isn't-quite-yet v4 release which contains significant changes that will require multiple adjustments to various parts of our CI. Even if v4 is released this month I reckon it will be next year before we can get around to dealing with it.
Not only is it a bad idea, it's actively breaking things as
@maincurrently points to the soon-to-be-released-but-isn't-quite-yet v4 release which contains significant changes that will require multiple adjustments to various parts of our CI. Even if v4 is released this month I reckon it will be next year before we can get around to dealing with it.