WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@jjerphan
Copy link
Member

@jjerphan jjerphan commented Apr 28, 2025

I wonder whether this could be automated.

I am only updating mamba because conda 25.4.0 is not out yet.

cc @hmaarrfk.

@jjerphan jjerphan changed the title Update to mamba 2.1.10 and conda-libmamba-solver 25.4.0 Update to mamba 2.1.0 and conda-libmamba-solver 25.4.0 Apr 28, 2025
Signed-off-by: Julien Jerphanion <[email protected]>
@jjerphan jjerphan changed the title Update to mamba 2.1.0 and conda-libmamba-solver 25.4.0 Update to mamba 2.1.0 Apr 28, 2025
@hmaarrfk
Copy link
Contributor

i don't have time to think about how to automate this. We have had many issues with "other projects" breaking the installer.

Generally, i think that conda moves too fast to really have meaningful releases here.

The main thing is that "the conda command should work"

If it does, and is slightly out of date, that is better than "not working because we didn't have time to test a release".

Feel free to make a PR to automate the "bumping of versions", but I don't want to "automate the making of releases" since those typically require "human thought" to assess quality.

@jjerphan
Copy link
Member Author

I agree.

Closing in preference of #777 since the scope changed.

@jjerphan jjerphan closed this Apr 28, 2025
@jjerphan jjerphan deleted the 25.4.0-0 branch April 28, 2025 14:11
@hmaarrfk
Copy link
Contributor

for others, we try to add testing to the build process, but it doesn't really mimic a "human" using the tool, rather it mimics our "expert understanding of how the tool should work in a CI".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants