-
Notifications
You must be signed in to change notification settings - Fork 16
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
bug with v2.0? #58
Comments
You should probably open an issue in the main mamba repo instead |
Thank you for opening this issue. The problem you are observing has been fixed in a release candidate of 2.0. I cannot reproduce the issue with micromamba 2.0 from conda-forge or from The problem is likely due to an integration issue between We are inspecting this issue. |
For now, explicitly setting the version of This can be done with: - name: Setup micromamba
uses: mamba-org/setup-micromamba@v1.9.0
with:
micromamba-version: '2.0.0-0' |
I believe I'm running into the same (or similar) parsing issue when creating a micromamba environment via CLI (using latest version of micromamba):
|
Hi @breakbotz, Can you open an issue on |
Created mamba-org/mamba#3472 |
Closing as it was not related to mamba but to GitHub action picking up a pre-release rather than 2.0. |
This used to work in my CI, but with the 2.0 release it breaks now:
Not sure if this is a bug or if I was abusing micromamba syntax. When I pinned the version back to
1.5.6-0
it worked again.Link to failed CI job: https://github.com/OpenFreeEnergy/openfe/actions/runs/11041820242/job/30672921965
The text was updated successfully, but these errors were encountered: