Rebuild for hdf5 1.14.4

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update hdf51144.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/11488800688 - please use this URL for debugging.}

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

[hmaarrfk]

@jaimergp did the filesystem change on windows and making the unicode test fail?

[jaimergp]

We haven't touched that part. The two things that changed on Windows were:

• Default to D:\ for the installation (and keep CONDA_BLD_PATH in the same drive to maximize performance). Since CONDA_BLD_PATH was already pointing to D: before that change, it shouldn't have an effect.
• Use micromamba to provision the base install. Again, not sure why that would make a difference. Checking main, it was already using micromamba in the last commit.

The only other thing I can think of is:

• Something changed in our Pythons. Weird that it would affect every version.
• Something changed in the Azure VM image. More likely?
• Upstream issue?

[hmaarrfk]

yeah i kinda want to rebuild hdf5 1.14.3 with newer compilers just to check these theories. thanks

[hmaarrfk]

I think this is the issue:

HDFGroup/hdf5#5037

[hmaarrfk]

Lets dicsuss conda-forge specific implications conda-forge/hdf5-feedstock#240

[jeongseok-meta]

Out of curiosity, is it acceptable to merge without updating Windows and address the issue later, possibly by creating a branch? I know this would increase complexity, but I was wondering if it's still something that can be considered.

[hmaarrfk]

No. Not acceptable since it would create an incompatibility for downstream packages that need h5py and HDF5 on windows.

Perhaps you can elaborate on why moving forward with this migration would be important for you on the issue I’ve opened on the HDF5 feedstock.