GitLab

In order for the update service to distinguish between
single-architecture x86_64 and arm64 builds as installed, the
architecture should be present in the tag that the update client
presents.

On its own, Keystone reports the architecture of the system it’s running
on, but for cases where the installed version may be native to the
system (an arm64 system running x86_64 Chrome under Rosetta
translation), where it may be preferable to retain the existing build
type for a period of time under our control, the architecture of the
installed product must also be reported. This information can also be
used to detect when a non-native version of Chrome is installed so that,
again under our control, we can direct an update to a more suitable
native version as appropriate.

This makes no changes to the tags used for single-architecture
mac-x86_64 builds. Whether this is advisable long-term is another
question, but for now, the prudent thing to do is to maintain the status
quo for the vast existing installed base. Any changes to that strategy
must be coordinated with the server-side configuration.

This changes the tags used for single-architecture mac-arm64 builds to
contain the “arm64” string, like “arm64”, “arm64-dev”, and “arm64-full”.

Bug: 1116601
Change-Id: I8e9dbc41285ea37018ebfd4e50b41bee985d9c8c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2496200Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820850}