At the moment, when a there are new changes made to master, Dockerhub and SingularityHub will automatically rebuild the image so that they always host the latest; however, the new image will not make its way to cvmfs unless someone remembers to do so.
Some kind of continuous integration/deployment technique could be used so that a new change on master will trigger a rebuild of the latest image and then a pull to cvmfs.