This was also see using 1.24.0 client on 1.18.x env. I suspect since modern juju doesn't have a prohibition against odd versions, it is happy to select 1.19.x
I think we need to remove 1.19. and all other odd versions from "released" streams to ensure historic devel versions cannot be placed into production without a human requiring it using agent-streams: devel.
This was also see using 1.24.0 client on 1.18.x env. I suspect since modern juju doesn't have a prohibition against odd versions, it is happy to select 1.19.x
I think we need to remove 1.19. and all other odd versions from "released" streams to ensure historic devel versions cannot be placed into production without a human requiring it using agent-streams: devel.