Unexpected plugin version selection after packer init -upgrade with ranged constraints
Teams using Packer want to ensure that image builds remain reproducible after a plugin upgrade while still being able to roll back to a known‑good state if the upgrade introduces issues. The documented recovery path relies on adjusting the version constraint in the required_plugins block and re‑running packer init, which installs plugins that satisfy the con