Thank you @Sanjaykumar030 for the potential contribution. I believe this script is intended for use with our GitHub Codespace configuration, where we can be confident of which OS we are using and what tools are available. Do you have a different use-case which requires it to be more general?

Thanks @rcomer for the feedback! Even though this script is mainly for Codespaces, the changes—version pinning, platform detection, and robust env name handling—make it safer and more deterministic. They prevent potential CI failures if dependencies or environments change, and don’t affect the existing Codespaces setup.

Sorry, I am still not following what this is for. If we are happy that it is OK in the Codespace setup, where is it going to run and [potentially] not be OK?

My main goal is to make our Codespaces CI more resilient. Pinning the version prevents a new micromamba release from unexpectedly breaking builds. As a bonus, this makes the script reliable for contributors replicating the environment locally. Without these changes, running the script outside Codespaces—on Linux/macOS/Windows—could fail due to version changes, unsupported platforms, or environment name parsing issues. These enhancements don’t affect Codespaces but make the setup safer and more deterministic.

What do you mean by "Codespaces CI"?

By "Codespaces CI," I mean the automated setup process in Codespaces that builds and configures dev environments reliably, similar to CI for consistency in contributions.

@rcomer you might want to take some other PR's of this author into consideration here, e.g.: scipy/scipy-stubs#862 (review)

Thanks @jorenham for confirming my suspicions.

Closing as probable AI spam.