Hello there!
You may check the current version of Updater 0.2.4-beta at
http://modx.com/extras/package/updater available at the repo. New and quite useful functionality (esp. if you maintain a lot of splattered modx installations at different hosting environments): the modx installations themselves can now
send you a notifier e-mail if they detect that there is a core update or are package updates available! Although a "digest" email with version information can be send on a regular base (eg. once a month).
I hope the Updater Extra helps people to keep their installations up-to-date and prevents a lot of installations out there which are out-of-date. Currently I am looking for a proper way to promote it a bit. Ideas?
Nevertheless I believe its functionality should definetly be part of the MODX core!
The previously named "
dirty details": Updater does check the github tags for new versions first and then searches for the corresponding zip-ball at modx.com. In fact it would be very useful to have a json or xml file (both!) containing versions information at modx.com - shouldn't be that hard to implement, can even be a static file to protect server performance. Currently you have no chance to automatically checks for new versions without beeing dirty.
The data there should also include a flag if a version contains security-related patches or if it is only a bugfix release (IMHO bugfix releases and security only releases should be separated in the future). This way users could choose to be informed about security updates only. The same goes for packages: currently there is no flag in package metadata, if a new version contains security fixes, package maintainers can only deprecate old versions.
@pepebe: is your regex still working as expected?