use newest micromamba

[wolfv]

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.

[xhochy]

We should setup a Github Action to auto-update that, I can do that soon.

[wolfv]

Thanks @xhochy that would hopefully allow us to catch these errors a bit earlier :( need to look into what's breaking here.

[wolfv]

We had problems building both mamba and micromamba on PPC64LE unfortunately.

[ericpre]

Now that mamba-org/mamba#961 is fixed, it should be possible to use micromamba on windows too?

This was disabled in #160, because of #158.

[wolfv]

@ericpre thanks for the reminder! :)

Are you running Windows? I am building miniforge with micromamba on Windows over here: https://github.com/wolfv/miniforge/actions/runs/1341613621

Artifacts to try should become ready in a couple of minutes.

[ericpre]

I will try in a virtual machine.

[ericpre]

This is working fine: I couldn't see anything wrong with the distribution and the shortcut menu is created. However, there is the following error message:

It may be related to https://github.com/conda/constructor/blob/f14fa91e1e363a029fffccb74c81618d27285bfb/constructor/nsis/main.nsi.tmpl#L904. It is possible that all start menu are created by default and that the menu_packages option of constructor is ignored. Does micromamba supports the --make-menus argument?

On this topic, there is conda/constructor#466.

[wolfv]

Nope, micromamba doesn't know about this argument yet. It should be quite trivial to add it though!

[ericpre]

Great, sounds good!
Removing menu when uninstalling doesn't work, see https://github.com/conda/constructor/blob/f14fa91e1e363a029fffccb74c81618d27285bfb/constructor/nsis/main.nsi.tmpl#L981

I don't know if other arguments are missing but just in case, the conda-standalone arguments for constructor are defined in https://github.com/conda-forge/conda-standalone-feedstock/blob/374ae2c27efcf5fd5cd38ddea316f59ff242067f/recipe/entry_point.py#L30-L51

[isuruf]

Thanks @xhochy that would hopefully allow us to catch these errors a bit earlier :( need to look into what's breaking here.

I think the most important part is to add a test to mamba-org/mamba repo to check that building an installer is supported. That way, errors are caught before the PRs are merged in mamba repo, instead of catching errors after they are pushed into mamba.