Changing the scope of a variable does not create the warning on deployment


  • Create a release which uses a library variable set
  • Modify the scope of a variable in the variable set
  • Deploy the release
  • No UI box comes up to warn you that your variables are out of date, and can be updated.

I haven’t tested this with non-library variable sets yet, but I would have thought the behaviour would be the same.


Thanks for reaching out. This only happens when modifying variables from a library set. The warning does work when modifying a variable from the project.

I’ve created a Github issue to have the warning in place when modifying a library variable