You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The repo still reports 2.0.1 as the latest version on the main GitHub page. I'm guessing these were supposed to be made from the date-based tags?
Also, where are there tags for each of the different binaries when the source is the same? This is making Homebrew/homebrew-core#195371 confusing. :) They seem the same, so maybe just historical.
The text was updated successfully, but these errors were encountered:
The latest reported version in https://github.com/mamba-org/mamba/releases is 2.0.2. 2.0.3 had some issues and was marked broken (so not mentioned in the GH page) - cf. #3576.
A 2.0.4 version containing the #3576 fixes and more will be released soonish.
Also, where are there tags for each of the different binaries when the source is the same? This is making Homebrew/homebrew-core#195371 confusing. :) They seem the same, so maybe just historical.
Not sure I understand what you mean. Tags are here with the corresponding commit they refer to.
There are four matching tags for each release: 2024.10.02, micromamba-2.0.2, mamba-2.0.2, and libmamba-2.0.2. All point at the same commit. That seems more confusing than having a v2.0.2 tag.
Not showing a release because it's broken is fine, and 2.0.2 is visible, so I think this is complete. Looking forward to 2.0.4, especially if it contains the fixes for brew. :)
The repo still reports 2.0.1 as the latest version on the main GitHub page. I'm guessing these were supposed to be made from the date-based tags?
Also, where are there tags for each of the different binaries when the source is the same? This is making Homebrew/homebrew-core#195371 confusing. :) They seem the same, so maybe just historical.
The text was updated successfully, but these errors were encountered: