I expect no updates to Free42 for a while. Of course you never know when something may come up, like a bug report or an idea for an improvement, but there is nothing on my to-do list at the moment, and I'm trying to focus on Plus42, where there is still work in the pipeline.
As for keeping your Free42 installation current, there are alternatives to the method I suggested. One approach would be to send an If-Modified-Since header explicitly, which would mean you wouldn't have to keep the old tarball around in order to prevent unnecessary downloads. Or you could use a HEAD request to check the last-modified date on the file.
If you're doing the check in a cron job, I do request you do not blindly download the file every time without any timestamp checks, since that would cause unnecessary load on my web server. As long as it's only a few people doing that, it wouldn't be an issue, but if the idea catches on, a significant increase in load could theoretically force me to upgrade to a more expensive usage tier with my hosting provider.
The best option would be if all Linux package maintainers updated their Free42 packages whenever I put out a new update, but unfortunately, most of them don't do that. As far as I'm aware, only the Arch Linux packages get prompt updates, usually within a week.