conda-forge.yml version numbers should be string, not float

[ytausch]

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.

To ensure compatibility with the new Pydantic schema of conda-smithy, version numbers should be strings, not floats in conda-forge.yml. Refer to conda-forge/conda-smithy#1756 (comment)

[conda-forge-webservices]

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) and found it was in an excellent condition.

[jakirkham]

Thanks Yannik! 🙏

Had some questions below

[jakirkham]

Am curious, why was this not read as a string before?

Though the bot was previously reading this ok

[jaimergp]

The context is at conda-forge/conda-smithy#1756 (comment)

[leofang]

Sorry, but I was under the impression that all values in conda-forge.yml are strings (ex: we have 10GiB above), so adding quotations or not does not make differences. Since when was this changed? I've read the linked issue but it was unclear to me.

[bdice]

YAML parsers try to interpret some numerical values as floats (presumably those conforming to some regex, or something like that). The “GiB” part of the 10GiB value makes it parse as a string. This was a big problem when Python 3.10 came out because many YAML files had - 3.10 which was interpreted as 3.1.

This fix seems reasonable to me.

[leofang]

I see, thanks for letting me know the parser quirks...