make date explicit; add links

Co-authored-by: jakirkham <[email protected]>

Author: h-vetinari

news/2025-05-29-cuda-118.md

@@ -10,17 +10,17 @@ for a while now, but many feedstocks (notably pytorch, tensorflow, onnx, jax etc
 have dropped CUDA 11.8 for many months already.
 
 Due to various constraints (details below), we are dropping CUDA 11.8 as a default
-version in our global pinning in one week. It will still be possible to opt into
+version in our global pinning on June 5th. It will still be possible to opt into
 building CUDA 11.8 on a per-feedstock basis where this is necessary or beneficial.
 
 <!-- truncate -->
 
 The above-mentioned contraints are mainly:
 
-- it complicates our pinning due to needing to switch images and compilers with 11.8.
+- it [complicates our pinning](https://github.com/conda-forge/conda-forge-pinning-feedstock/issues/6967) due to needing to switch images and compilers with 11.8.
 - it keeps us from [migrating](https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/7005)
   to newer CUDA 12.x versions necessary to support new architectures.
-- it's not compatible with VS2022, which is due to become the default toolchain on windows
+- it's [not compatible with VS2022](https://github.com/conda-forge/conda-forge.github.io/issues/2138#issuecomment-2916743741), which is due to become the default toolchain on windows
   in conda-forge soon (the previous VS2019 has reached end-of-life more than a year ago).
 - it complicates our infrastructure in several places, due to the big differences between the
   before/after of the new CUDA architecture.