revert a change to a supporting source module, especially if you weren't sure it changed. Your refactoring may change the directory locations of files in the build so now the project .MAK has changed since last release and thus needs to be promoted. What if a trial refactoring that didn't work out? Your team deserves all the change bookkeeping assistance that your SCM tools can give you.
My experience is that the current tools and integrated development environments do support these situations pretty well, but only if you take the time to configure them for these maintenance cycle processes before you start cutting code. Retrofitting SCM and compiler options across all the teams' PCs is not fun, and is just plain disruptive.