Pin SUNDIALS to 7.5 and add migrator to 7.6

[Saransh-cpp]

Checklist

• Used a personal fork of the feedstock to propose changes
• 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 @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

XRef #8392

Pin SUNDIALS to v7.5 and add migrator for v7.6.

I am not sure what the right thing to do here is, given that several repositories use very different versions of SUNDIALS, such as:

• https://github.com/conda-forge/fmipp-feedstock/blob/main/recipe/meta.yaml: 2.7.*
• https://github.com/conda-forge/pycvodes-feedstock/blob/main/recipe/meta.yaml: >=5.3,<6.0
• https://github.com/conda-forge/sunode-feedstock/blob/main/recipe/meta.yaml: >=5.5.0,<6
• https://github.com/conda-forge/muq-feedstock/blob/main/recipe/meta.yaml: <7

cc: @traversaro

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

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/23899471762. Examine the logs at this URL for more detail.}

[traversaro]

Thanks @Saransh-cpp ! Something I forgot to mention in my issue, was that you need to pin the version down the detail specified in the run_exports invocation of the package, see https://github.com/conda-forge/sundials-feedstock/blob/17857af8bc4cc5904276e21ee79d399b32995696/recipe/recipe.yaml#L46 . So I guess we need to pin sundials to 7.5 and do the migration to 7.6 .

I am not sure what the right thing to do here is, given that several repositories use very different versions of SUNDIALS, such as:

https://github.com/conda-forge/fmipp-feedstock/blob/main/recipe/meta.yaml: 2.7.*
https://github.com/conda-forge/pycvodes-feedstock/blob/main/recipe/meta.yaml: >=5.3,<6.0
https://github.com/conda-forge/sunode-feedstock/blob/main/recipe/meta.yaml: >=5.5.0,<6
https://github.com/conda-forge/muq-feedstock/blob/main/recipe/meta.yaml: <7

Thanks for investigating this! I guess that ideally to ensure all these packages are co-installable they should share the same sundials version used here, but even if some specific feedstocks restrict their sundials version they want.

[Saransh-cpp]

Thanks for the help, @traversaro! I have updated the pin to 7.5 and have added a migrator for 7.6.

[traversaro]

Can you name the migration sundial76.yml ?

[Saransh-cpp]

Ahah, you beat me to it. I was about to push the commit.