Patch Tuesday for July 2026 - #52938
Conversation
* Visual Studio: 18.6.2 -> 18.8.0 * 7-Zip: 26.01 -> 26.02 * Git for Windows: 2.54.0.windows.1 (image) and 2.55.0.windows.2 (tool metadata) -> 2.55.0.windows.3 * CMake: 4.3.3 -> 4.4.0 * PowerShell: 7.6.2 -> 7.6.3 * Azure CLI: 2.87.0 -> 2.88.0 * AzCopy: 10.32.4 -> 10.32.6 * CUDA Toolkit: 13.2.0 -> 13.3.1 * cuDNN: 9.20.0.48 -> 9.24.0.43 * .NET SDK: 10.0.301 -> 10.0.302 * Google Cloud SDK: 567.0.0 -> 576.0.0 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was added back in microsoft#15598 in attempt to switch from gfortran to ifort. Unfortunately ifort has been outright removed (in favor of Intel's new LLVM based fortran compiler, ifx) and it looks like we never actually landed a switch to ifort in the first place. See also https://community.intel.com/t5/Blogs/Tech-Innovation/Tools/Deprecation-of-The-Intel-Fortran-Compiler-Classic-ifort/post/1541699 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5dd71ff5-2168-4bd2-bd0b-f7d1c5a52a86
* Ubuntu Noble base: 2026-01-13 (Android) and 2026-04-10 (Linux) -> 2026-06-10 * Eclipse Temurin JDK 17: 17.0.18+8 -> 17.0.19+10 * Android command-line tools: 14742923 (20.0) -> 15859902 (22.0) * Android platform 36: revision 1 -> revision 2 * Android platform-tools: 36.0.2 -> 37.0.0 * CUDA Linux packages: 13.2 -> 13.3 * PowerShell for Linux arm64: 7.6.0 -> 7.6.3 * Node.js: 22.x -> 24.x * Android container tag: 2026-02-10 -> 2026-07-15 * Linux container tags: 2026-04-20 -> 2026-07-15 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 84b12170-f063-4d4a-89f8-378673cbade4
Replace SAS-based asset downloads with the prototype VM user-assigned identity and verify legacy TLS is disabled without mutating cipher settings. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Rely on the Windows Server image defaults instead of checking obsolete Schannel registry keys. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
PR Build cancelled, CI Build running https://dev.azure.com/vcpkg/public/_build/results?buildId=134533&view=results |
|
Billy O'Neal (@BillyONeal) As you update the Linux image: Is it possible to update to Resolute (see #52748)? |
I've already started the CI run and there's already a lot of stuff being changed this month so I'm trying to avoid opening that can of worms; I was considering looking at that around October (That is, around when 26.10 comes out so they've had a normal release time to work things out) I have heard about lots of fallout from the GCC 14 update I'm trying to avoid being the first person touching, if that makes sense. |
Good point, forgot that this update also mean GCC will be updated. What do you think about already creating just a PR with resolute, so we can see which ports are needing updates? |
Add VCPKG_PROVIDED_FORTRAN as a triplet opt-in. When enabled, vcpkg_find_fortran selects vcpkg's architecture-matched MinGW gfortran instead of probing the host; when disabled, Windows triplets leave compiler selection to their toolchain. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…s upstream build system; worked around this by just updating to a version not from 2022. GPT 5.6 Sol found and fixed a couple of issues which were filed upstream as ezEngine/ezEngine#1991 and ezEngine/ezEngine#1992 . [popsift] More missing headers from CUDA changes. Submitted upstream as alicevision/popsift#188 [mongo-c-driver, opencv4] Apply upstream fixes for CUDA 13.3 and CMake 4.4.
Is there a specific thing we need Resolute for? |
See #52748 |
That's interesting enough to not wait until October but probably not worth doubling the work for this update this month. |
|
Just a question: Since #51210 we have CUDA 13.x. As far as I can see, this patch PRs causes mostly a world rebuild - but sadly not for all ports, as, e.g., FLANN is broken with CUDA 13.x (see #52761), which is not detected by the CI until now, because of probably caching. Billy O'Neal (@BillyONeal) Do you have an idea, how vcpkg could detect used system dependency, so a rebuild will be triggered if there is a change? |
No, the last CUDA update involved a full (CI) rebuild, caching was not used. I think the more likely reason is that |
|
SunBlack (@SunBlack) Got first results back, very glad I did not try to combine the Resolute update in here 😅
|
3 participants
Summary
Refresh the vcpkg CI images, containers, and tool metadata for July 2026.
prototype-vmuser-assigned managed identity.Version updates