Open joelanford opened 3 months ago
/assign
/assign
@itroyano and @dhoover103, I'm refactoring this area of code in #1033, so you may want to hold off or branch off of that PR.
@joelanford mentioned that he has already fixed it, so assigning it to him to cross check.
I cross checked. I don't think I did fix this actually. My mistake!
I have a scenario setup with 6.0.1 installed, where I updated the spec.version to 6.0.0 with upgrade policy enforcement enabled.
I got the following error message:
This makes it sound like:
I expected something along the lines of (where the list of best available successors would be sugar on top):