-
Notifications
You must be signed in to change notification settings - Fork 104
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
Cut the conda-lock v3.0.0 release #725
Comments
For anyone following this, this has taken a bit longer than I hoped. I am waiting for a resolution of #720 which is currently blocked by mamba-org/mamba#3467. |
Thanks for following this! I am also waiting for micromamba to stabilize to cut a new updated release for my users. It seems the change they think will fix it was merged last week. Hopefully they will cut a release soon. |
Also blocked on the regression #730 |
We are still gradually inching closer. For example, on the #720 front, mamba-org/mamba#3467 has been resolved, but it's now blocked by mamba-org/mamba#3628. |
I was just wondering about that yesterday (since I was testing the pre-release of conda-lock to see if it solved an issue a user was having -- it does which is great :)). So to summarize, the current blockers are:
Is that it? Hopefully 3628 can be solved quickly (it seems more like a "whoops" type of bug) and I can try looking at #730. |
Thanks @romain-intel!!! You are correct that those are the (known) blockers. (I also personally want to get in #708 so that I can mention it in the v3 release notes, but it's not actually a blocker.) I agree with your assessment of 3628. I haven't managed yet to look into a fix for #730. It would be incredible if you could help with that!!! |
Thanks to mamba-org/mamba#3681 the just-released v2.0.5 of micromamba will likely unlock #720 / #724. |
Still blocked on #720 / #724. 😞 Thanks to v2.0.5 we're getting further, but have now hit a new snag with mamba-org/mamba#3693. |
I want to let everyone know my thinking regarding the release process of conda-lock v3 and also prepare the release notes. Comments welcome!
My current impression is that the recent release of mamba/micromamba v2 has caused a bit of chaos, and that it's prudent to wait for things to stabilize somewhat before cutting this release. (Ideally this specifically means merging #720 and #724.) On the other hand, I expect this release to resolve many outstanding bugs and blockers, so many will want to install as soon as possible.
I'd like to encourage the eager and brave to install from the main branch. Installing via pip should look something like
pipx install --force 'git+https://github.com/conda/conda-lock@main'
where
pipx
can be replaced withpip
andmain
can be replaced with a current Git SHA.Alternatively, from an
environment.yml
, you can add the following to your dependenciesFirst draft release notes, up to and including #633:
[explanation of major changes goes here]
[say something nice about pixi, and link to the migration docs]
TODO: categorize the below, remove bot contributions, combine followups, check the authors, e.g. srilman is missing
What's Changed
Breaking changes
New features
Bugfixes
Documentation
Maintenance
New Contributors
The text was updated successfully, but these errors were encountered: