-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include "fn" in fake_conda_environment for mamba>=1.4.6 compatibility #453
Include "fn" in fake_conda_environment for mamba>=1.4.6 compatibility #453
Conversation
✅ Deploy Preview for conda-lock ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
e6e7eb1
to
03c8539
Compare
Should fix conda#452 with mamba>=1.4.6
This looks good from my side. Before merging let's see if Jonas responds in #452. |
…package record found!`" This reverts commit 03c8539.
@maresb, with the I am still keeping |
Apply suggestions from code review Co-authored-by: Ben Mares <[email protected]>
Answer: I can unpin Micromamba independently, presumably thanks to using |
Description
See #452. The initial goal of this (draft) PR is to provide evidence about the fact that including the file name ("fn") in the fake environment packages' JSON file makes mamba>=1.4.6 happy