-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VS 17.10; == VS2022 Update 10 #79
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 ( |
Something weird is happening here:
|
Aside from CMake and the conda-build issue we're running into here, we'll also need to wait for 17.10 to appear in the Azure images:
|
While the documentation has not been updated (the PR is still open actions/runner-images#9990), I can confirm that Visual Studio 17.10 (with MSVC 14.40) has been deployed to Azure a few days ago. Our nightly builds started failing on Tuesday night (TileDB-Inc/conda-forge-nightly-controller#104 (comment)). Here is an example build log:
|
@conda-forge/vc, given the breakage for VS2022 users, I think we should merge this soon, PTAL. |
Co-authored-by: Marcel Bargull <mbargull@users.noreply.github.com>
…nda-forge-pinning 2024.06.06.20.20.38
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
Fixes #72, though there might be more places we have to update; for now I'm keeping
vcver
at14.3
, due toNeeds to wait for: