Add libpython run dependency for Python 3.14 on Windows

[antonwolfy]

Problem

The main branch build fails on win_64_python3.14 with an OverLinkingError:

ERROR (mkl_umath,_ufuncs.cp314-win_amd64.pyd): Needed DSO python314.dll found in ['libpython==3.14.7=..._102_cp314']
  .. but ['libpython'] not in reqs/run, (i.e. it is overlinking)

Cause

conda-forge python-feedstock PR #894 split the shared Python library into a separate libpython output, and follow-up PR #907 (merged 2026-08-30) actually relocated python*.dll from the python package into libpython on Windows (build _101 → _102).

The _ufuncs/_patch_numpy extension modules link python314.dll (unavoidable on Windows). Neither the python nor the libpython output carries a run-export that credits libpython, so consumers must declare it explicitly.

This is specific to Python 3.14+: the libpython shared-library output exists only on the python-feedstock main branch (3.14/3.15). On 3.13 and earlier, python313.dll is still shipped inside the python package, so those builds are unaffected (and pass).

Change

• Add libpython # [win and py>=314] to run.
• Bump build number 1 → 2 (win 3.14 @ b1 failed while the other variants @ b1 already uploaded).

[conda-forge-admin]

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 (recipe/meta.yaml) and found it was in an excellent condition.

[antonwolfy]

@conda-forge-admin, please rerender

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

It appears you are making a pull request from a branch in your feedstock and not a fork. This procedure will generate a separate build for each push to the branch and is thus not allowed. See our documentation for more details.

Please close this pull request and remake it from a fork of this feedstock.

Have a great day!

[antonwolfy]

Closing — this was opened from a branch on the feedstock instead of a fork. Reopened from a fork as #5.