Bug with identified pinnings in use?

[jaimergp]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

I'm starting to see pari added to the .ci_support files of noarch packages that do not depend on pari at all, but do mention napari in the meta.yaml:

• https://github.com/conda-forge/napari-feedstock/pull/69/files#diff-999d2f034982a9a29cc0f5a5340497f76ff9243576ea74e5954ec5ad5f32b74cR9
• https://github.com/conda-forge/napari-plugin-manager-feedstock/pull/7/files#diff-999d2f034982a9a29cc0f5a5340497f76ff9243576ea74e5954ec5ad5f32b74cR9

I wonder if this is due to a new bug in conda-smithy that reads the pinnings wrong when rerendering? Or maybe some interaction with the recently released conda-build 24.9.0?

Installed packages

Re-rendered with conda-build 24.9.0, conda-smithy 3.40.1, and conda-forge-pinning 2024.09.27.18.25.24

Environment info

See CI at https://github.com/conda-forge/napari-plugin-manager-feedstock/actions/runs/11079114601/job/30787583490