We’ve noticed recently that if we go to deploy a previous release in Octopus we are no longer getting the following prompt if the variable sets have changed
Thanks for getting in touch, and welcome! My apologies for the confusion we caused by this warning no longer being present. This was a conscious decision to remove the warning due to conflicts with the Configuration as Code feature that allows you to version control your variables and deployment process.
I’m going to bring this up internally to discuss and try to think of any way to improve this (at least for non-version controlled projects), as there have been a number of users who relied on this prompt. For now at least, the only workaround is to manually check and compare the release snapshots, or create a new release.
Please let me know if you have any questions or concerns going forward.