Sorry, I still don't understand. The post say you need to do

1. Have the code recognize the new value. Get that shipped everywhere.

2. Have the code do something reasonable when the new value appears. Get that shipped everywhere.

3. Start emitting the new value.

My proposal is

1. Have the code recognize the new value. Have the code do something reasonable when the new value appears. Get that shipped everywhere.

2. Start emitting the new value.

If the user has to manually update, and might refuse to do so, the problem exists under both the 3 step and the 2 step process. So nothing is gained by using the 3 step process.

If the client and backend are updated independently, that should still be fine with the 2 step process. The 2 step process says "Get that shipped everywhere", meaning shipped to both the client and the backend.