Review Results

Comment

The change is a straightforward version bump in .SRCINFO from 150.0.7871.100 to 150.0.7871.114 with no other metadata changes. On its face this does not introduce new sources, scripts, dependencies, permissions, or packaging behavior. Since only the .SRCINFO hunk is in scope and it contains no executable content, I see no security issue in this diff alone.

@@ -1,6 +1,6 @@
 pkgbase = google-chrome
 	pkgdesc = The popular web browser by Google (Stable Channel)
-	pkgver = 150.0.7871.100
+	pkgver = 150.0.7871.114
 	pkgrel = 1
 	url = https://www.google.com/chrome
 	install = google-chrome.install

Comment

The change is a straightforward version bump of the Google Chrome binary package from 150.0.7871.100-1 to 150.0.7871.114-1, with the corresponding SHA-512 checksum updated. The source remains the official HTTPS dl.google.com release URL, and no new build steps, scripts, patches, or privilege-related artifacts are introduced in this hunk. Based on the provided diff alone, there are no obvious supply-chain or persistence red flags.

@@ -20,10 +20,10 @@ pkgbase = google-chrome
 	optdepends = kwallet: for storing passwords in KWallet
 	options = !emptydirs
 	options = !strip
-	source = https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_150.0.7871.100-1_amd64.deb
+	source = https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_150.0.7871.114-1_amd64.deb
 	source = eula_text.html
 	source = google-chrome-stable.sh
-	sha512sums = 40fe3ec9292fb5124fabdfb2c6c58ca6d3d353297372bcab8240ab981af575c755886eaa3a7beb755c3713215a889e505d6458a40aed3cda499d3d79117d55f1
+	sha512sums = d9db8b204380b384df25d1eaf36c51d5d29c263c061973f37bd3389ba1ce9afc0d4dfc469cfaccd6dc6ac40d3f7871320cfe9d8c49826e3e3e12cf2baf865095
 	sha512sums = a225555c06b7c32f9f2657004558e3f996c981481dbb0d3cd79b1d59fa3f05d591af88399422d3ab29d9446c103e98d567aeafe061d9550817ab6e7eb0498396
 	sha512sums = de02b498a4b5b93e21622c8dba57befe795d733a04656be911cc38e28bfef0e20470450f44be523bbde8d4de28f79c10434846ca01fc2a2f4e67707b79332f94
 

Comment

The diff only bumps pkgver from 150.0.7871.100 to 150.0.7871.114 in PKGBUILD. No build logic, sources, checksums, install scripts, permissions, or dependency changes are introduced by this hunk. On its face this is a routine upstream version update with no added security red flags in the provided change.

@@ -7,7 +7,7 @@
 # or use: $ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | grep -A1 "Package: google-chrome-stable" | awk '/Version/{print $2}' | cut -d '-' -f1
 
 pkgname=google-chrome
-pkgver=150.0.7871.100
+pkgver=150.0.7871.114
 pkgrel=1
 pkgdesc="The popular web browser by Google (Stable Channel)"
 arch=('x86_64')

Comment

The change only updates the SHA-512 checksum for the upstream Google Chrome .deb source file. The source URL remains the official HTTPS dl.google.com location, and no build logic, install script, permissions, or execution behavior is altered. This is a normal integrity update consistent with a new upstream package release, with no obvious security red flags in the provided hunk.

@@ -35,7 +35,7 @@ _channel=stable
 source=("https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-${_channel}/google-chrome-${_channel}_${pkgver}-1_amd64.deb"
 	'eula_text.html'
 	"google-chrome-$_channel.sh")
-sha512sums=('40fe3ec9292fb5124fabdfb2c6c58ca6d3d353297372bcab8240ab981af575c755886eaa3a7beb755c3713215a889e505d6458a40aed3cda499d3d79117d55f1'
+sha512sums=('d9db8b204380b384df25d1eaf36c51d5d29c263c061973f37bd3389ba1ce9afc0d4dfc469cfaccd6dc6ac40d3f7871320cfe9d8c49826e3e3e12cf2baf865095'
             'a225555c06b7c32f9f2657004558e3f996c981481dbb0d3cd79b1d59fa3f05d591af88399422d3ab29d9446c103e98d567aeafe061d9550817ab6e7eb0498396'
             'de02b498a4b5b93e21622c8dba57befe795d733a04656be911cc38e28bfef0e20470450f44be523bbde8d4de28f79c10434846ca01fc2a2f4e67707b79332f94')