Fix typo in menuinst v1 json file

[mrclary]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• [ ] Reset the build number to 0 (if the version changed)
• [ ] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [ ] Ensured the license file is being packaged.

Fixes spyder-ide/spyder#22790

[mrclary]

@conda-forge-admin, please rerender

[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. I do have some suggestions for making it better though...

For recipe/meta.yaml:

• PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

[conda-forge-admin]

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

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11671887584.}

[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.

[ccordoba12]

@mrclary, did you manually check that this fixes the problem for old menuinst versions?

[dalthviz]

Just in case, I think there is a config (store_build_artifacts) that can be set to enable downloading the package as an Azure pipeline artifact (https://conda-forge.org/docs/maintainer/conda_forge_yml/#azure). Maybe it could be worthy to enable that to check changes to the feedstock on PRs?

[mrclary]

@mrclary, did you manually check that this fixes the problem for old menuinst versions?

Not yet.

Just in case, I think there is a config (store_build_artifacts) that can be set to enable downloading the package as an Azure pipeline artifact (https://conda-forge.org/docs/maintainer/conda_forge_yml/#azure). Maybe it could be worthy to enable that to check changes to the feedstock on PRs?

That would be very useful. Do we need to make that change in a separate PR and merge that in first, or can that be included in the current PR?

[dalthviz]

That would be very useful. Do we need to make that change in a separate PR and merge that in first, or can that be included in the current PR?

I think doing the change here should trigger the upload here but if that doesn't work we can try opening a PR only for that and then updating this one after that gets merged :+1:

[mrclary]

I think doing the change here should trigger the upload here but if that doesn't work we can try opening a PR only for that and then updating this one after that gets merged 👍

I'll give a try.

[mrclary]

@dalthviz @ccordoba12 I don't see any artifacts on Azure. Did I do something wrong?

[ccordoba12]

@conda-forge-admin, please rerender

[ccordoba12]

Maybe a rerender is necessary?

[mrclary]

Maybe a rerender is necessary?

That seemed to work. I can download artifacts!

[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. I do have some suggestions for making it better though...

For recipe/meta.yaml:

• noarch: python recipes should almost always follow the syntax in our documentation. For the host section of the recipe, you should almost always use python {{ python_min }}.* for the python entry. You may need to override the python_min variable if the package requires a newer Python version than the currently supported minimum version on conda-forge.
• noarch: python recipes should almost always follow the syntax in our documentation. For the run section of the recipe, you should almost always use python >={{ python_min }} for the python entry. You may need to override the python_min variable if the package requires a newer Python version than the currently supported minimum version on conda-forge.
• noarch: python recipes should almost always follow the syntax in our documentation. For the test.requires section of the recipe, you should almost always use python ={{ python_min }} for the python entry. You may need to override the python_min variable if the package requires a newer Python version than the currently supported minimum version on conda-forge.

[mrclary]

@conda-forge-admin, please rerender

[mrclary]

@mrclary, did you manually check that this fixes the problem for old menuinst versions?

I've now tested on my Windows VM. With menuinst=1.4.20 and the build artifact, Spyder installs without error and the shortcuts are created.