Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
One thing to note: with the new workflow based on the
msys2/setup-msys2action, we now depend on a proprietary Windows runner in the CI.
I didn't make up my mind about this yet.
I would not worry about this, because the current state of affairs is that this isn't tested, and adding additional proprietary CI is something I would personally describe as "easy come, easy go". As long as it works, it works, and does no harm. If it turns out to be unmaintainable, or breaks when transferring to a different software forge (sourcehut, gitlab, gitea...), then you just delete it again.
But there's no particular reason to think it will stop working any time soon, and it provides free bug reports about things breaking, so why not. :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.