Google regularly updates Chrome with new features, security updates, and more. Chrome downloads these updates and installs them automatically. But how often does that happen? It depends that the Chrome update process is quite complicated.
Important Stable Versions Every Six Weeks
Chrome is developed outdoors and anyone can install the unstable versions. But when it comes to the stable branch, builds are released about every six weeks. For example, Chrome 73 was released on March 1
Although it was not always the case – originally Chrome updates were quite sporadic – the Chrome team committed to six-week release intervals in 2010 and has been relatively steady ever since. Sometimes releases appear in four weeks, others in eight. In general, however, it is always somewhere around the six-week mark.
It's also worth noting that Google can not adjust the stable publishing schedule around Chrome to "no meeting weeks" and holidays.
Security and Bug Fixes When Needed 
Although you can count on periodic major releases, bug fixes and security updates are much less predictable . Crawling the Stable version stable update change logs shows that there have been three updates since the release of Chrome 73 on March 12, and there is no noticeable interval between releases. This is pretty natural for these types of updates.
But at least you can count on Chrome to get some bug fixes and / or security updates between major releases.
Chrome automatically installs both major stable updates and minor updates as they become available. You can open the menu at any time and search for updates in Help> About Google Chrome and install them right away.
When will the next version be released?
If you're curious about the next major release of Chrome being released on the stable channel, check out the Chrome Platform Status website. This also shows when the current stable version became stable, as well as information about the unstable versions of Chrome being tested in the beta and dev channels.
Chrome OS also updates every six weeks
Like the major browser releases, Chrome OS is updated about every six weeks. While the version numbers and features generally match those of your browser, Chrome OS versions typically run one week after the browser update.
For example, Chrome 73 was released on March 12, but Chrome OS 73 did not land on the stable channel until March 19.
Otherwise, Chrome OS follows the same basic publishing process as the Chrome OS browser. The main exception here is that the rollout schedule may vary depending on the Chrome OS device – it can take a few weeks for some devices to be hit, as each device differs slightly.
How Chrome Update Channels Work
There are several four areas of Chrome development: Canary, Dev, Beta, and Stable. These are in the order from the least stable (Canary) to the most stable (er, stable).
The features that first appear in Canary should end up in the stable channel – so many users want to do this to get a glimpse of the future running of multiple versions of Chrome on their computers. It's also very cool to see how the features evolve through the release channels.
Every six weeks, a Canary build is set as the new milestone stabilization branch. Here new features and improvements are developed and implemented. It stays here for another two weeks and is then moved to the first beta version. After two more weeks in the beta channel, a feature freeze will be set up. This means that all features intended for the stable channel should complete the code. This is also the reason why some features originally planned for a particular stable release are pushed back to the next big build.
During the remaining four weeks of beta, new builds will be released weekly until the stable release. On Thursday, before the stable version is released (which is usually on Tuesdays), the latest beta build becomes the publication candidate. At this time, all the stable functions are completed and merged with the stable branch.
Google has another build called "Stable Refresh" for testing bug fixes. This is a stable release that is outside the regular release schedule and is used to fix critical issues that just can not wait.
Stable releases are slowly rolling out
All stable Chrome releases follow a staged release schedule (except for Linux, which was moved to 100% at the time of release). The desktop versions – Mac and Windows – are released in four states: 5%, 15%, 50% and 100%. Therefore, different users receive updates at different times.
Android has a similar schedule, but with an extra step: 1%, 5%, 15%, 50%, and 100%.
iOS follows a different pattern than the other two, with the update being available to all users for a period of seven days: Day 1: 1%; Day 2: 2%; Day 3: 5%; Day 4: 10%; Day 5: 20%, Day 6: 50%; and day 7: 100%.
These staged rollouts allow Google to identify issues before they reach all users, stopping and resuming the rollout once the issue is resolved.