incorporate review suggestions

Co-Authored-By: Mark Harfouche <[email protected]>

Author: h-vetinari

docs/maintainer/knowledge_base.md

@@ -534,6 +534,7 @@ requirements:
   run:
     - python
 ```
+For more details about numpy see the dedicated [section](#building-against-numpy).
 
 With MPI, openmpi is required for the build platform as the compiler wrappers are binaries, but mpich is not required as the compiler wrappers are scripts (see [example](https://github.com/conda-forge/mpi4py-feedstock/blob/743d379c4a04/recipe/meta.yaml#L37)):
 
@@ -771,7 +772,7 @@ host:
 
 At the time of writing (June 2025), above is equivalent to the following,
 
-```yaml
+```yaml title="recipe/conda_build_config.yaml"
 host:
   - numpy 2.*
 ```

news/2025-05-20-numpy-2-migration-closure.md

@@ -3,12 +3,17 @@
 NumPy 2.0 was a big change (the first major version in 15 years). For more than a year, we
 have been migrating feedstocks from NumPy 1.x to NumPy 2.x, and while not every affected
 feedstock has been done, we are planning to conclude the migration at the end of May.
+Note that NumPy 2 support is required for feedstocks that intend to support Python 3.13
+and above.
 
 For feedstocks that are not compatible with v2.x yet, this means you will have to add
 
 ```yaml
 numpy:
-  - 1.26  # or similar
+  - 1.26  # or 1.25
 ```
 
-to your `recipe/conda_build_config.yaml`, and then rerender.
+to your `recipe/conda_build_config.yaml`, and then rerender.Pins below 1.25 are not possible
+if your feedstock supports Python 3.12, as NumPy 1.25 was the first version with support for
+that Python version (and it will not be possible going forward to pin different NumPy versions
+for different Python versions).