micromamba 2.1.1

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

release notes

Release: 2.1.1 (libmamba, mamba, micromamba, libmambapy)
Enhancements:

[libmamba] Use Simdjson ondemand parser instead of DOM parser by @Klaim in Use Simdjson ondemand parser instead of DOM parser mamba-org/mamba#3878

Bug fixes:

[libmamba] Fix segfault in error messages by @AntoinePrv in Fix segfault in error messages mamba-org/mamba#3912
[libmamba] fix: Requalify warning when parsing the "mod/etag" header by @jjerphan in fix: Requalify warning when parsing the "mod/etag" header mamba-org/mamba#3910
[micromamba] Make self-update a command for micromamba only by @jjerphan in Make self-update a command for micromamba only mamba-org/mamba#3906
[libmamba] Fix nushell env for Windows by @cvanelteren in Fix nushell env for Windows mamba-org/mamba#3880
[libmamba, micromamba] fix: Give precedence to repodata when constructing repodata_record files by @jjerphan in fix: Give precedence to repodata when constructing repodata_record files mamba-org/mamba#3901
[libmamba, micromamba] feat: add sha256 flag to list command by @SandrineP in feat: add sha256 flag to list command mamba-org/mamba#3885
[libmamba, libmambapy] Fix VersionSpec globs by @AntoinePrv in Fix VersionSpec globs mamba-org/mamba#3889
[micromamba] hotfix: in integration tests assume xtensor is v0.26 by @Klaim in hotfix: in integration tests assume xtensor is v0.26 mamba-org/mamba#3898

CI fixes and doc:

[all] Explicit API and ABI stability commitments by @AntoinePrv in Explicit API and ABI stability commitments mamba-org/mamba#3913
[all] Add minimal citation information for mamba by @jjerphan in Add minimal citation information for mamba mamba-org/mamba#3914

Maintenance:

[libmambapy] DX: libmambapy import in build tree by @AntoinePrv in DX: libmambapy import in build tree mamba-org/mamba#3916
[libmamba] Internally add flag for switching MatchSpec parser by @AntoinePrv in Internally add flag for switching MatchSpec parser mamba-org/mamba#3905
[micromamba] Some test isolation by @AntoinePrv in Some test isolation mamba-org/mamba#3900
[libmamba] Ready Libsolv for C++20 by @AntoinePrv in Ready Libsolv for C++20 mamba-org/mamba#3899
[all] build(deps): bump codecov/codecov-action from 4 to 5 by @app/dependabot in build(deps): bump codecov/codecov-action from 4 to 5 mamba-org/mamba#3896
[all] ci: Adapt code coverage workflow by @jjerphan in ci: Adapt code coverage workflow mamba-org/mamba#3890

---

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.

[pwhiteusa]

I use micromamba on Mac M4 OS Sequoia, installed via hombrew. The self-update function is no longer working?

❯ micromamba --version
2.1.1

❯ micromamba self-update
The following argument was not expected: self-update
Run with --help for more information.

Check this documentation: https://mamba.readthedocs.io/en/latest/installation/micromamba-installation.html

It states:

"""
Self updates

Once installed, micromamba can be updated with

micromamba self-update
"""

[p-linnane]

@pwhiteusa We don't like tools that update themselves, but as far as I can tell we aren't doing anything to disable that functionality. You may want to reach out to upstream. This is our entire install block which builds the software:

  def install
    args = %W[
      -DBUILD_LIBMAMBA=ON
      -DBUILD_SHARED=ON
      -DBUILD_STATIC=OFF
      -DBUILD_MAMBA=ON
      -DCMAKE_INSTALL_RPATH=#{rpath}
    ]

    system "cmake", "-S", ".", "-B", "build", *args, *std_cmake_args
    system "cmake", "--build", "build"
    system "cmake", "--install", "build"
    # Upstream chooses names based on static or dynamic linking,
    # but as of 2.0 they provide identical interfaces.
    bin.install_symlink "mamba" => "micromamba"
  end

[pwhiteusa]

I updated from 2.1.0 to 2.1.1 and the problem seems to have gone. Thanks for the quick reply @p-linnane !