Skip to content

Cut the conda-lock v3.0.0 release #725

Description

@maresb

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 with pip and main can be replaced with a current Git SHA.

Alternatively, from an environment.yml, you can add the following to your dependencies

dependencies:
- git  # Only necessary when Git is unavailable at the system level
- pip
- pip:
  - conda-lock @ git+https://github.com/conda/conda-lock@main

First 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions