Closed zaneselvans closed 7 months ago
Thanks for the report! Looks like we have a regression. :disappointed:
Please let me know if you figure out a reliable way to locally reproduce this.
For context, these are virtual packages.
Ah, I see the problem. Our toposort function was not just sorting, but also filtering out the virtual packages. I'll fix this...
Checklist
What happened?
After updating to
conda-lock
v2.5.0 some odd new packages are showing up in ourconda-lock.yml
when it is regenerated via a GitHub action:I noticed that they exist because the lack of a
hash
value is causing thesetup-micromamba
GitHub action to fail with the following error:However, no packages named
__osx
or__glibc
appear in theconda-lock.yml
when I generate it locally using a similar command. The only obvious differences between the two environments are:conda-lock --micromamba
while locally I'm usingconda-lock --mamba
. The command being used to generate the conda lockfiles / environment files:However, running the above commands locally using
--micromamba
does not result in the__glibc
or__osx
packages appearing inconda-lock.yml
Conda Info
Conda Config
Conda list
Additional Context