Previously, early in the morning the build system blindly updated to the latest tip of tree, built it, generated updates, and made them available on the proper channel–even if there were no changes since the last time. This was inefficient for users, a poor use of build system resources, and unnecessarily contributed to update fatigue for less-active channels.

The new behavior makes it so automated morning builds only occur when the code or dependent localizations have actually changed since the last update.