Skip to content

Commit 6396b8c

Browse files
h-vetinarijaimergp
andauthored
final touches
Co-authored-by: jaimergp <[email protected]>
1 parent cf4c185 commit 6396b8c

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/maintainer/knowledge_base.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -778,8 +778,8 @@ host:
778778
- numpy 2.*
779779
```
780780

781-
See the pinning repository for what the pinning corresponds to at any given time
782-
[https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/conda_build_config.yaml#L742](https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/conda_build_config.yaml#L742)
781+
See the pinning repository for
782+
[what the pinning corresponds to](https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/conda_build_config.yaml#L742) at any given time.
783783

784784
In either case, the actual runtime requirements are determined through numpy's
785785
run-export, which is:

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
NumPy 2.0 was a big change (the first major version in 15 years). For more than a year, we
44
have been migrating feedstocks from NumPy 1.x to NumPy 2.x, and while not every affected
5-
feedstock has been done, we are planning to conclude the migration at the end of May.
5+
feedstock has been done, we are planning to conclude the migration in one week.
66
Note that NumPy 2 support is required for feedstocks that intend to support Python 3.13
77
and above.
88

0 commit comments

Comments
 (0)