fix: builds fail with ModuleNotFoundError for hatchling

[iisakkirotko]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• 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.

Builds for new versions fail with

ModuleNotFoundError: No module named 'hatchling'

Even though hatchling is listed in all dependencies. Trying some stuff here.

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

[iisakkirotko]

@conda-forge-admin, please rerender

[dhirschfeld]

Try hatchling=1.22.2

[dhirschfeld]

They shouldn't be using exact pins upstream:
https://github.com/widgetti/solara/blame/04cbe23a5cbd1124df0afa541c6d61939bc5a3cf/pyproject.toml#L2

[iisakkirotko]

Try hatchling=1.22.2

Doesn't seem to work either... It seems to me that something has changed about the build step - it seems to skip the installation of dependencies completely for the solara package.

They shouldn't be using exact pins upstream: https://github.com/widgetti/solara/blame/04cbe23a5cbd1124df0afa541c6d61939bc5a3cf/pyproject.toml#L2

What's even weirder is that apparently for the different subpackages of solara we use different versions, pinning ==1.22.2 for some, but only >=0.25 for others.

[dhirschfeld]

conda-build bug? I'd definitely report that to @conda-forge/core as, IIUC we shouldn't be touching those scripts since they will get overwritten with every rerender.

[hmaarrfk]

But if you can reference or open an issue in conda-build it may be appropriate to break the rules!

[dhirschfeld]

xref: conda/conda-build#5444