VS 17.14#100
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15766372540. Examine the logs at this URL for more detail. |
…nda-forge-pinning 2025.06.19.05.31.58
|
@conda-forge/vc, VS 17.14 has started rolling out in the runner-images. Please review at your earliest convenience. I raised #98 almost a month ago, but my hopes of getting #95 in first did not pan out (otherwise I would have raised this PR right after), so now I'm opening it as a minimal change to fast-track things. If breakage becomes severe enough (given that we're now defaulting to VS2022), I will merge, considering the blast radius. |
|
Hmm, this is a good reason to not go to the latest VS year. This is something to consider next time we update the VS major year |
Yeah, I agree. I did think about it already this time, but considered it non-critical because 17.14 is the last minor of the 17.x series. |
It seems the images with VS 17.14 are starting to be rolled out, and many windows jobs failing because of it
Closes #98