Pin mamba/micromamba <2.6.0 until 2.6 is supported (#907) - #921
Merged
Conversation
✅ Deploy Preview for conda-lock ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
maresb
changed the title
maresb
marked this pull request as ready for review
June 27, 2026 14:57
conda-lock does not yet support mamba/micromamba 2.6.0 (tracked in conda#907). The routine dependency update in conda#911 bumped the dev environment to mamba 2.6.2, which broke CI on main (last green: 2026-05-20). Pin the dev-environment solver to `mamba <2.6.0` and the CI MICROMAMBA_VERSION to the last pre-2.6 release (2.5.0-2), and regenerate pixi.toml to match. Temporary workaround, to be reverted in conda#907. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Regenerated via `conda-lock lock --update mamba`, downgrading mamba/libmamba 2.6.2 -> 2.5.0 (and their dependency subtree: simdjson, openssl, certifi, ca-certificates, libmsgpack-c, typing-extensions). No other packages changed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
maresb
force-pushed
the
chore/pin-mamba-lt-2.6
branch
from
June 27, 2026 15:05
d331a7a to
ead51c9
Compare
maresb
pushed a commit
to maresb/conda-lock
that referenced
this pull request
Jul 4, 2026
Remove the stopgap pins from conda#921 (see also conda#907): this branch delivers the mamba/micromamba 2.6 support the pins were waiting for, and CI must run micromamba >=2.6.0 to actually exercise the hierarchical package cache layout end-to-end. - ``MICROMAMBA_VERSION`` back to ``latest`` in ``test.yml`` and ``integration-test.yml``. - ``mamba`` unpinned in ``pixi.toml`` and ``environments/dev-environment.yaml``. The committed lockfiles remain valid: they resolve mamba 2.3.2, which satisfies both the pinned and unpinned specs, and they were generated from source files identical to the post-revert state (conda-standalone included, no pin), so their content hashes still match. A relock is still desirable to pull mamba >=2.6.0 into the dev environment so the e2e ``mamba`` parametrization exercises the new solver rather than 2.3.2.
maresb
pushed a commit
to maresb/conda-lock
that referenced
this pull request
Jul 5, 2026
Remove the stopgap pins from conda#921 (see also conda#907): this branch delivers the mamba/micromamba 2.6 support the pins were waiting for, and CI must run micromamba >=2.6.0 to actually exercise the hierarchical package cache layout end-to-end. - ``MICROMAMBA_VERSION`` back to ``latest`` in ``test.yml`` and ``integration-test.yml``. - ``mamba`` unpinned in ``pixi.toml`` and ``environments/dev-environment.yaml``. The committed lockfiles remain valid: they resolve mamba 2.3.2, which satisfies both the pinned and unpinned specs, and they were generated from source files identical to the post-revert state (conda-standalone included, no pin), so their content hashes still match. A relock is still desirable to pull mamba >=2.6.0 into the dev environment so the e2e ``mamba`` parametrization exercises the new solver rather than 2.3.2.
maresb
pushed a commit
to maresb/conda-lock
that referenced
this pull request
Jul 5, 2026
Remove the stopgap pins from conda#921 (see also conda#907): this branch delivers the mamba/micromamba 2.6 support the pins were waiting for, and CI must run micromamba >=2.6.0 to actually exercise the hierarchical package cache layout end-to-end. - ``MICROMAMBA_VERSION`` back to ``latest`` in ``test.yml`` and ``integration-test.yml``. - ``mamba`` unpinned in ``pixi.toml`` and ``environments/dev-environment.yaml``. The committed lockfiles remain valid: they resolve mamba 2.3.2, which satisfies both the pinned and unpinned specs, and they were generated from source files identical to the post-revert state (conda-standalone included, no pin), so their content hashes still match. A relock is still desirable to pull mamba >=2.6.0 into the dev environment so the e2e ``mamba`` parametrization exercises the new solver rather than 2.3.2.
maresb
pushed a commit
to maresb/conda-lock
that referenced
this pull request
Jul 5, 2026
Remove the stopgap pins from conda#921 (see also conda#907): this branch delivers the mamba/micromamba 2.6 support the pins were waiting for, and CI must run micromamba >=2.6.0 to actually exercise the hierarchical package cache layout end-to-end. - ``MICROMAMBA_VERSION`` back to ``latest`` in ``test.yml`` and ``integration-test.yml``. - ``mamba`` unpinned in ``pixi.toml`` and ``environments/dev-environment.yaml``. The committed lockfiles remain valid: they resolve mamba 2.3.2, which satisfies both the pinned and unpinned specs, and they were generated from source files identical to the post-revert state (conda-standalone included, no pin), so their content hashes still match. A relock is still desirable to pull mamba >=2.6.0 into the dev environment so the e2e ``mamba`` parametrization exercises the new solver rather than 2.3.2. Verification: grep confirms no mamba/micromamba version pins remain (`git grep -n 'MICROMAMBA_VERSION\|mamba =' .github/ pixi.toml environments/`); the pins being reverted were introduced by conda#921 solely to dodge the 2.6.0 cache-layout break this branch fixes.
maresb
pushed a commit
to maresb/conda-lock
that referenced
this pull request
Jul 7, 2026
Remove the stopgap pins from conda#921 (see also conda#907): this branch delivers the mamba/micromamba 2.6 support the pins were waiting for, and CI must run micromamba >=2.6.0 to actually exercise the hierarchical package cache layout end-to-end. - ``MICROMAMBA_VERSION`` back to ``latest`` in ``test.yml`` and ``integration-test.yml``. - ``mamba`` unpinned in ``pixi.toml`` and ``environments/dev-environment.yaml``. The committed lockfiles remain valid: they resolve mamba 2.3.2, which satisfies both the pinned and unpinned specs, and they were generated from source files identical to the post-revert state (conda-standalone included, no pin), so their content hashes still match. A relock is still desirable to pull mamba >=2.6.0 into the dev environment so the e2e ``mamba`` parametrization exercises the new solver rather than 2.3.2. Verification: grep confirms no mamba/micromamba version pins remain (`git grep -n 'MICROMAMBA_VERSION\|mamba =' .github/ pixi.toml environments/`); the pins being reverted were introduced by conda#921 solely to dodge the 2.6.0 cache-layout break this branch fixes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
conda-lock does not yet support mamba/micromamba 2.6.0 — that work is tracked in #907.
The routine dependency update in #911 bumped the dev environment to mamba 2.6.2, which broke CI on
main(last green: 2026-05-20). Until 2.6 support lands, this keeps conda-lock pinned to a supported solver:environments/dev-environment.yaml: pinmamba <2.6.0and relock (mamba/libmamba 2.6.2 → 2.5.0; only the mamba dependency subtree changes)pixi.toml: regenerated to match (keepstest_generate_pixi_tomlpassing).github/workflows/{test,integration-test}.yml: pinMICROMAMBA_VERSIONto2.5.0-2, the last pre-2.6 releaseThis is a temporary workaround, to be reverted in #907 once 2.6 is supported.
🤖 Generated with Claude Code