Review Results

Comment

The change only bumps the package version in .SRCINFO from 150.0.7871.124 to 150.0.7871.128. No source URLs, build logic, install scripts, dependencies, or permissions are altered in this diff. On its face this is a routine metadata update with no security-relevant behavior change.

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

Comment

The change only bumps the pinned upstream Google Chrome .deb from 150.0.7871.124-1 to 150.0.7871.128-1 and updates the corresponding SHA-512 checksum in .SRCINFO. The source remains the official HTTPS dl.google.com URL, with no new build steps, scripts, or packaging behavior introduced. This is a routine version/checksum refresh with no evident security impact in the diff reviewed.

@@ -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.124-1_amd64.deb
+	source = https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_150.0.7871.128-1_amd64.deb
 	source = eula_text.html
 	source = google-chrome-stable.sh
-	sha512sums = 711e74171beed23affd6c6b6283370545c6530710e3242242cbc997612d0be243480d3c0ec797e5f0ff541ab80b2a7d596f2abdf709a8c8e3ae1caf7813a953e
+	sha512sums = 523895aa6c20303d31079367c317ecaff1c7ce075bd36983fca694823125de3ee01f02f98880acbbff25f540b468d1130502aa0e6f80a293bb453890a1c46893
 	sha512sums = a225555c06b7c32f9f2657004558e3f996c981481dbb0d3cd79b1d59fa3f05d591af88399422d3ab29d9446c103e98d567aeafe061d9550817ab6e7eb0498396
 	sha512sums = de02b498a4b5b93e21622c8dba57befe795d733a04656be911cc38e28bfef0e20470450f44be523bbde8d4de28f79c10434846ca01fc2a2f4e67707b79332f94
 

Comment

This change is a simple version bump in PKGBUILD from 150.0.7871.124 to 150.0.7871.128 with no other packaging logic changes. Based on the provided diff hunk, there are no new sources, build steps, install scripts, permissions changes, or other security-relevant modifications. Risk is minimal.

@@ -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.124
+pkgver=150.0.7871.128
 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 Google Chrome .deb source to match a new upstream release artifact. The source URL remains HTTPS and points to the official Google download location, with no new build steps, scripts, or privilege-related changes. I don’t see any added supply-chain or execution risk in this diff beyond the normal trust in the upstream binary package already present in the PKGBUILD.

@@ -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=('711e74171beed23affd6c6b6283370545c6530710e3242242cbc997612d0be243480d3c0ec797e5f0ff541ab80b2a7d596f2abdf709a8c8e3ae1caf7813a953e'
+sha512sums=('523895aa6c20303d31079367c317ecaff1c7ce075bd36983fca694823125de3ee01f02f98880acbbff25f540b468d1130502aa0e6f80a293bb453890a1c46893'
             'a225555c06b7c32f9f2657004558e3f996c981481dbb0d3cd79b1d59fa3f05d591af88399422d3ab29d9446c103e98d567aeafe061d9550817ab6e7eb0498396'
             'de02b498a4b5b93e21622c8dba57befe795d733a04656be911cc38e28bfef0e20470450f44be523bbde8d4de28f79c10434846ca01fc2a2f4e67707b79332f94')