Added support for mamba up to 1.4.4

[millsks]

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.

boa version stays the same. Only rebuilt with support for mamba 1.4.4.

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

[millsks]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/boa-feedstock/actions/runs/5418654009.

[wolfv]

I am sorry, I can't merge this because of a bug in mamba. I'll update the range once we've been able to test in the boa repository

[jakirkham]

Maybe we should convert this to draft so that others see this was tried already and there is a reason it is not merged

[millsks]

Thanks @wolfv and @jakirkham. I was wondering if it was a bug with mamba specific to 1.4.4 and boa 0.15 together or is the bug present in previous versions of mamba? I only ask because the range for mamba in boa 0.14 is >=1.0,<1.5.

[ThomasGandilhon]

Hello, any update on this ?
This PR is ultimately blocking conda-forge/miniforge#462.

I struggle to find the details of the aforementioned issues related to mamba / boa. Could you please direct me to the issue(s) ?

[hmaarrfk]

this could be closed?