This is a feature that I did not think would be needed, but with the latest version being released I was not able to see the update from the web UI until bliss was restarted. Since I run bliss on CentOS, there is no provided init scripts and the one I have created only starts bliss so the easiest and quickest way for me to reboot bliss is to bounce my server (which also serves media via SubSonic).

The update process restarts bliss at the end so I assume the code for a restart is already written and could easily be incorporated into the UI.