back

by pentagrama·5y ago·view on hn ↗
Not totally related, but someone know if exist an RSS feed to follow the stable Firefox releases? Can't find it on this page.

This Firefox changelogs are awesome to know big improvements and new features on a surface level.

For Chrome I didn't find a proper way to follow the releases even if it has some RSS feeds, I follow the RSS feed of Chrome Releases blog [1] with a tag filter [2] but can't exclude the several point releases, and also the changelogs are not very informative [3]. And the Chrome blog [4] I get some feature announcements but is a mix bag.

[1] https://chromereleases.googleblog.com

[2] http://googlechromereleases.blogspot.com/feeds/posts/default...

[3] https://chromereleases.googleblog.com/2021/01/stable-channel...

[4] https://blog.google/products/chrome/

2 comments
https://hg.mozilla.org/mozilla-unified/tags https://hg.mozilla.org/mozilla-unified/atom-tags https://hg.mozilla.org/mozilla-unified/rss-tags

And here's my lua script that uses notify-send to notify me of new releases: https://gist.github.com/folknor/32f703b270c6ad72bc12d98feb2f... I modified it slightly before posting it here, but it's mostly useless unless you're me :-D Because when I write shell scripts (which I always do in lua), I always use my fork of luash (from my github), and I don't imagine anyone else has it. It's easy enough to rewrite the script to not require it, though. Also, the other obscure dependency it uses is lua2xml, which is notoriously unreliable, but I still use it in all my shell scripts that interact with XML.

I forgot to mention: before running the script (as if anyone ever would), create a file called "notified" in the same folder with the content "85.0.0" without the quotes, or whatever recent firefox release version you want to build from. The script also needs to be able to write to this file.
I've updated the gist so it now can be used without my luash fork, and can be used with ((luash+curl) || luasec || lua-curl). Just for fun :-)
Thank you! That's perfect! And a bit ironic that the RSS feed is on a Google product aka the company that kill Google Reader.
Take a look at my reply to the OP