What I recommend here is that:
1. the immediate issue can be solved for 1.24 and 1.25 by ensuring the --no-auto-upgrade arg is used
2. we will improve the behaviour of how auto upgrades are done for 1.26
3. in Juju 2.0, we will not auto upgrade by default
What I recommend here is that:
1. the immediate issue can be solved for 1.24 and 1.25 by ensuring the --no-auto-upgrade arg is used
2. we will improve the behaviour of how auto upgrades are done for 1.26
3. in Juju 2.0, we will not auto upgrade by default