Build conda-libmamba-solver packages on defaults and conda-forge about conda-libmamba-solver HOT 4 CLOSED

See conda-forge/staged-recipes#17923

We need a new conda release to support the code paths needed by the conda-libmamba-solver, and that's why it fails, but the recipe will be essentially the same (with the lower bounds for conda set at 4.12, I guess).

from conda-libmamba-solver.

Before we get to that point of doing the conda release, we should build the package in place and upload it to anaconda.org using the canary-release action we have in https://github.com/conda/actions, would that work? E.g. can we specify a channel from which to get the conda build in the recipe?

Since I thought we can now:

• Build a conda canary package using the "build::review" label, which is then uploaded to the conda-canary channel.
• Implement the recipe inline in this repo to make use of the same technique, basically having both conda (with libmamba logic) and conda-libmamba-solver in the conda-canary channel?

from conda-libmamba-solver.

Opened #5

from conda-libmamba-solver.

Closing since this is fixed.

from conda-libmamba-solver.