Updating environment variables does not cause a new AWS Lambda version to be published

There is an open ticket on this for over 2 years with no progress:

Question I have, does anyone have a workaround for this in mind? How you would overcome this missing behaviour?