[Magic CLI]: Unexpected downgrade of MAX when installing community mojo package

[dmeaux]

Issue description

Honestly, I'm not sure this even warrants an issue as I haven't been able to reproduce it, but I thought you might want to know or be aware of it. Here's what happened:

I installed hue and mojmelo from the community packages using magic 0.5.0. My project was originally on the latest nightly build (max = ">=25.1.0.dev2024121705,<26"). The first time I added the first package (mojmelo), magic added the package and downgraded my max to be >=24.5.0,<=25.0a0 without giving me an error or prompting me to downgrade.

I then removed mojmelo and max and then added max back by itself, which upgraded max to the latest nightly build, as expected. Then when I added mojmelo the second time, it gave me the expected error that it couldn’t solve the conda requirements of ‘default’ ‘linux-64’ and basically that I needed max >= 24.5.0,<25.0a0.

So, I downgraded max and reattempted to add mojmelo, which worked as expected. So did the follow-on add of hue.

I also upgraded magic to the 0.6.0 prerelease and redid the above steps with no issues. That is, I was still not able to replicate the unexpected downgrade behavior I experienced the first time.

Steps to reproduce

I have not been able to reproduce this issue so far.

Version Info

- magic 0.5.0
- Linux-64
- Fedora 40
- x86-64 AMD