Right actions taken from baselines do not update when you update the baseline, which is good in a way because if someone is fiddling about with a baseline you would not want the change to the baseline to propagate to the endpoints until the baseline editor was sure the change is something they want.
It would be nice however to have a button that would allow the editor to propagate the changes to the baseline to all the actions based off of the baseline. But even then what if one baseline action was targeted to one group of computers to execute at one time and another action was targeted to execute at another time. So this new update-propagation functionality would need to allow the baseline editor to choose which actions to propagate the changes to.
Keeping it simple, we basically say, if you make a change to a baseline and you need to re-deploy this new baseline on, take a new action.