Google updates Chrome regularly with new features, security updates, and more. Chrome downloads the updates and installs them automatically. But how often does it happen? That's because the Chrome update process is quite complicated.
Large Stable Versions Every Six Weeks
Chrome is developed in the open and everyone can install the unstable versions. But when it comes to the stable branch, buildings are released about every six weeks. For example, Chrome 73 was released on March 12 and Chrome 74 was released on April 23 – six weeks to the day.
While not always here-originally, Chrome updates were quite sporadic – the Chrome team engaged in six-week trigger intervals back in 2010 and has been relatively consistent ever since. Sometimes, editions come in four weeks, other times in eight. But in general, there is always somewhere right around the six week mark.
It is also worth noting that Google can adjust the stable release schedule around Chrome "no meeting weeks" and holidays.
Security and bug fixes when needed 
While you can pretty much expect large versions to come out regularly, bug fixes and security updates are much less predictable. Just crawling through the update release update update shows that there have been three updates since Chrome 73 was released on March 12, and there is no noticeable interval between each release. It's pretty much for the course for these types of updates.
But in any case, you can expect Chrome to get some bug fixes and / or security updates between large versions.
Chrome installs both large stable updates and minor updates automatically when they are available. You can always open the menu and go to Help> About Google Chrome to search and install updates immediately as well.
When will the next version come?
If you are curious when the next large version of Chrome will be released to the stable channel, check out the Chrome Platform Status website. This also shows when the current stable version became stable and 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 versions, Chrome OS is updated about every six weeks. While the version numbers and features generally reflect the one corresponding to their browser, the Chrome OS edition usually corresponds to a 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 release as the Chrome OS browser. The primary exception here is that the expansion time may vary depending on any Chrome OS device. It may take a few weeks to hit some units, because each one is slightly different.
How Chrome Update Channels Work
There are four branches of Chrome development: Canary, Dev, Beta and Stable. They are in order from least stable (Canary Islands) to the most stable (um, Stable).
Eventually, the features that first appear in the Canary Islands should get to the stable channel, which is why many users who want to get a glimpse of the future run multiple versions of Chrome on their computers. It is also really cool to see the functions ahead as they go through the trigger channels.
Every six weeks, a canary building is set as the new milestone stabilization branch. Here are new features and improvements designed and implemented. It remains here for another two weeks, and at that time it is being driven into the first beta version. After another two weeks in the beta channel, a function freeze is put in place – this means that all functions intended for the stable channel must be coded. This is also why we see that some functions that were originally planned for a certain stable trip are driven back to the next large building.
For the remaining four weeks of the beta scene, new buildings are released weekly until the stable is released. Thursday before the stable version is launched (which usually happens on Tuesdays), the latest beta building becomes the release candidate. At that time, all stable functions were completed and merged with the stable branch.
To test bug fixes, Google also has another design called "Stable Refresh." It is a stable release that falls outside the regular release and is used
Stable releases roll out slowly
All stable Chrome releases follow a scheduled release schedule (save for Linux, which is 100% printed at the time of release). Desktop versions, Mac and Windows, are released in four states: 5%, 15%, 50% and 100%. This is why different users receive updates at different times.
Android follows a similar schedule, though with a further step: 1%, 5%, 15%, 50% and 100%.
iOS follows a different pattern from the other two, with the update rolling out to all users during a seven day period: 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 problems before they reach all users, thus stopping the rollout and resuming it when the problem is corrected.