Chrome Releases
googlechromereleases.blogspot.com · Company blog · on HN since 2009
Google's official release notes for Chrome, listing stable, beta, and security updates by version and channel.
What HN saysHN commenters use it to check current stable versions and security fixes, and say it comes closest to a readable changelog at Google.
76HN people shared it
37linked it in comments
46stories submitted
305story points
6 years agolast shared
2009people per year2026
Most-shared posts
- 1Release updates from the Google Chrome team5 people · 1 points · first shared 2010 · discussion on HN
- 2Chrome Releases: Stable Channel Update3 people · 7 points · first shared 2015 · 1 comments on HN
- 3Google Chrome 38 now available for download3 people · 4 points · first shared 2014 · discussion on HN
- 4Google Chrome Beta update: Fullscreen support [OSX Lion] and Native Client2 people · 22 points · first shared 2011 · 14 comments on HN
- 5Google Chrome 39 Released2 people · 9 points · first shared 2014 · discussion on HN
- 6Google Chrome rolls out $14470.70 worth of security patches2 people · 8 points · first shared 2011 · 1 comments on HN
- 7Chrome 34 released to stable2 people · 4 points · first shared 2014 · 1 comments on HN
- 8Google Chrome 10 released2 people · 1 points · first shared 2011 · discussion on HN
- 9Windows users get nice-looking fonts now (and much more)2 people · 1 points · first shared 2014 · discussion on HN
- 10Google fixes Chrome security hole, awards $60k2 people · 1 points · first shared 2012 · discussion on HN
- 11Stable channel update2 people · first shared 2013
- 12Stable channel update 242 people · first shared 2010
- 13Chrome 14 released1 people · 69 points · first shared 2011 · 46 comments on HN
- 14Google Chrome Releases: Stable Channel Update1 people · 46 points · first shared 2011 · 14 comments on HN
- 15Google Chrome 4.0 (with Extension Support) released for Windows1 people · 19 points · first shared 2010 · 10 comments on HN
What HN people wrote when they linked it
simonsarris · 2014-03-03
Do any teams in Google write a human readable change log?
The only one I know of that comes close is the Chrome team, which gets by with a blogspot[1] that sometimes has nice lists of the changes (sometimes in list form, sometimes in a paragraph with loads o' commas), and sometimes says stuff like:
> A partial list of changes in this build is available in the SVN revision log http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?…
And here with Go 1.2.1 we get this[2].
It's not a huge deal in this case, but if you release a version and link to it and want us to know why its significant, it would be nice to find out why in English instead of SVN-ese.
Compare this to the great, readable version that Firefox offers[3]
~~~
[1] http://googlechromereleases.blogspot.com/
[2] https://code.google.com/p/go/source/list?name=release-branch.go1.2&…
[3] https://www.mozilla.org/en-US/firefox/27.0.1/releasenotes/
pentagrama · 2021-02-26
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/-/Stable%…
[3] https://chromereleases.googleblog.com/2021/01/stable-channel-update-fo…
[4] https://blog.google/products/chrome/
ikeboy · 2015-08-06
46 is not stable (the current stable release is 44, see http://googlechromereleases.blogspot.com/). Also, if you want Chrome Beta on android you can go here: https://play.google.com/store/apps/details?id=com.chrome.beta
georgemcbay · 2014-05-04
As the person who reported issue #337746:
http://googlechromereleases.blogspot.com/2014/04/stable-channel-update…
I agree that this would be a big win.
If this type of rendering were in place it would protect the user in most cases even when a secondary issue like the one I reported exists in the full rendering code. Well worth the minor inconvenience of having to click the 'chip' to show the full url if you happen to need to see/copy it.
cheeaun · 2013-10-04
Would be better to know which channel of Chrome got updated (Dev, Beta, Stable?) and also for which platform (Android, iOS, Desktop browser, Chrome OS, Chromecast?). The site to check up on this http://googlechromereleases.blogspot.com/
InclinedPlane · 2010-02-01
Stable and beta channels are 4.0.x, only the dev. channel is 5.0, it's not a beta release.
See: http://googlechromereleases.blogspot.com/
profmonocle · 2016-12-03
Seems to be disabled by default. I can enable the new behavior by going to chrome://flags/#prefer-html-over-flash, but when I set that flag to "default" Flash works the same as before.
Has Google confirmed this actually made it into Chrome 55? Their blog post[1] about the release doesn't mention it. One of the article's sources is from earlier this year, and the developer thread they link to has been quiet for about a month. I wonder if plans changed and they're leaving it behind a flag for now, or if they're A/B testing it somehow.
[1] https://googlechromereleases.blogspot.com/2016/12/stable-channel-updat…
randomfool · 2016-10-25
https://googlechromereleases.blogspot.com/2016/10/stable-channel-updat…
Chrome 54 is now in stable.
0x0 · 2016-10-05
Looks like current ad specs allow third party javascript and iframes - http://storage.pardot.com/52662/23178/Spotify_Ad_Specs.pdf - linked from https://spotifyforbrands.com/us/formats/
Didn't the desktop apps use to bundle an embedded flash player before? I can't remember but it wouldn't have surprised me if they did.
Wonder what kind of html5/js engine they use for ads these days. (not that it matters, they are all swiss cheese security-wise, especially so if they aren't tracking upstream daily. If you think the sandbox is foolproof, well, just have a look at chromeos - time since last webpage-to-persistent-root exploit is currently about: 6 days https://googlechromereleases.blogspot.no/2016/09/stable-channel-update… )
the_why_of_y · 2016-05-17
Here's Mozilla Firefox, search for "use-after-free", "memory safety hazard".
https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/
Here's Google Chrome, search for "buffer overflow", "Use after free", "out-of-bounds":
http://googlechromereleases.blogspot.com/search/label/Stable%20updates
Edit: Chromium bug tracker talks to me now, query for "use-after-free" has 2157 results:
https://bugs.chromium.org/p/chromium/issues/list?can=1&q=type%3Dbu…
bossx · 2016-02-08
That's a Chrome for Android feature, you can stop it from your notifications. http://googlechromereleases.blogspot.ca/2013/02/chrome-for-android-upd…
async5 · 2015-08-07
And even latest here http://googlechromereleases.blogspot.co.il/2015/07/stable-channel-upda… - 5 of them has pdfium
eeZi · 2015-05-03
The Git tree is already outdated: https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/log/, last commit 2015-04-09.
In the meantime, Chromium 42 has been released: http://googlechromereleases.blogspot.de/2015/04/stable-channel-update_… including a bunch of security fixes.
altcognito · 2015-01-02
Since you asked:
Most Chrome and Firefox releases (in my experience) have been relatively minor, and focused on security and bugs. Lets take a look at the last 4 releases of Chrome:
http://googlechromereleases.blogspot.com/2014/11/stable-channel-update…
http://googlechromereleases.blogspot.com/2014/10/stable-channel-update…
http://googlechromereleases.blogspot.com/2014/09/stable-channel-update…
http://googlechromereleases.blogspot.com/2014/08/stable-channel-update…
What argument could be made that longer release cycles would mean less bugs? Is there going to be better QA? More stringent testing? Why would shorter release cycles mean less testing?
No, longer release cycles would mean similar number of bugs, and security holes would just sit out there longer. Chrome and Firefox is an example of doing it right.
minimaxir · 2014-10-10
> Thanks to recent efforts at Netflix and Canonical, Ubuntu now supports watching Netflix with Chrome version 37.
Funnily, Chrome 38 is now out (http://googlechromereleases.blogspot.com/2014/10/stable-channel-update… after an emergency release, which shows how long these press releases take to plan.
genesem · 2014-07-10
http://googlechromereleases.blogspot.ru/2014/07/flash-player-update.ht…
read the comments princess..
andor · 2014-06-15
Recently Google has added a built-in translation feature to Chrome that has some usability issues. Since these issues haven’t been fixed in the past couple of releases, they might be here to stay.
Built-in Google Translate was added in Chrome 4.1 in 2010:
http://googlechromereleases.blogspot.de/2010/03/windows-beta-update-tr…
cauterize · 2014-06-10
Does it strike anyone else as odd that they don't highlight security updates as Chrome does? Example, http://googlechromereleases.blogspot.com/2014/05/stable-channel-update… Maybe it's psychological, but I like the reassurance security is a focus for Chrome.
mda · 2014-02-05
Oh sure, they are not magic smoke indeed. Still, how do you explain that Use after free bugs are marked Critical in Firefox but High on Chrome? Seems like Chrome is doing a little bit better in security department.
https://www.mozilla.org/security/known-vulnerabilities/firefox.html
http://googlechromereleases.blogspot.ch/search/label/Stable%20updates
mace · 2013-11-15
This should no longer be true. Chrome v31 (http://googlechromereleases.blogspot.com/2013/11/stable-channel-update… added SCTP support for reliable DataChannels and allowing compatibility with Firefox.
markdodwell · 2013-10-04
Nice idea.
Right now, it is just checking the Chrome release blog Stable channel to see if a release was pushed on the current day http://googlechromereleases.blogspot.com/2013/07/stable-channel-update…
abarth · 2013-07-10
Chrome 28 is available now on the stable channel:
http://googlechromereleases.blogspot.com/2013/07/stable-channel-update…
The update is rolling out gradually. If you would like to make sure you're on the latest version, you can select "About Google Chrome" from the "Chrome" menu on Mac. That will take you to a page that shows you which version you're running and checks for updates.
As the release blog mentions, the Flash update is rolling out via the component updater, which updates Flash independently of the rest of Chrome.
CrazedGeek · 2013-03-09
The update was Monday: http://googlechromereleases.blogspot.com/2013/03/stable-channel-update…
thematt · 2013-01-15
Why does it have to be specifically RCE? Here are some lists of Firefox's and Chrome (fixed) security vulnerabilities. Browse the lists and you'll find plenty of critical issues related to Javascript.
http://www.mozilla.org/security/known-vulnerabilities/firefox.html
http://googlechromereleases.blogspot.com/2009/08/stable-update-securit…
gaving · 2012-06-10
alexandere · 2012-05-15
Overview of security fixes:
http://googlechromereleases.blogspot.com/2012/05/stable-channel-update…
pinwale · 2012-05-01
Google will be adding support for the Cr-48 in Chrome OS 20.
From the comments: http://googlechromereleases.blogspot.com/2012/04/dev-channel-update-fo…
semenko · 2012-03-09
The Chrome Release blog says it's fixed: http://googlechromereleases.blogspot.com/2012/03/chrome-stable-channel…
And that the SVN commit history is available: http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?…
But I don't see any commit that look even remotely related to this exploit. What's up?
mithaler · 2011-10-22
Chrome just added an API for this in their dev builds, for Native Client at least. http://googlechromereleases.blogspot.com/2011/10/dev-channel-update_18…
simonbrown · 2011-09-16
The blog posts mention that the bugs are only kept private until most people are up to date, but some never seem to be made public. For example:
http://googlechromereleases.blogspot.com/2011/01/chrome-stable-release…
Some of the bugs (e.g. 66560) still give me a 403 (although some are accessible).