Teams tested and signed off on last weeks Chrome update. As I was publishing to production today I'm getting errors indicating Google has released a newer version.
Is there a way I can publish the legacy version while the even newer version is being tested?
Thanks for posting your question here. You can still publish updates like that if you can get the installer and provide it in a Local Source folder, as outlined in this doc:
Publish Manually Downloaded Products in Patch for SCCM
Of course, be cautious about where you obtain the installer. The same validation will take place in publishing from that local folder, though, so it will verify the hash matches what's expected.
Retrieving data ...