Comment
This is a routine version bump for a binary package, with only updated SHA-256 checksums for the upstream Brave release archives. The sources remain HTTPS GitHub release URLs, there are no new build-time downloads, scripts, patches, privilege changes, or packaging logic changes. Based on the diff provided, I see no security red flags beyond the inherent trust in upstream binary blobs, which is unchanged from the prior package.
@@ -35,8 +35,8 @@ source_aarch64=(${pkgname}-${pkgver}-aarch64.zip::https://github.com/brave/brave
noextract=(${pkgname}-${pkgver}-x86_64.zip ${pkgname}-${pkgver}-aarch64.zip)
sha256sums=('75a87dd17b42fcc6f27adfd16c82bed1c08e9251b07d2012f8d49f7412fa1d00'
'c07276b69c7304981525ecb022f92daf7ae125a4fb05ac3442157b50826e257a')
-sha256sums_x86_64=('ace5409dfb5a6238e3c09576fab56ef76d31e00ed6d62f10d0b41685ab3fe200')
-sha256sums_aarch64=('1b542c83474770a94606e03e4a57536d586b905a22861a3440095729f388e7fc')
+sha256sums_x86_64=('8b115b4242b54b743c05ab73fb4ffe2ace5d9e59756ce0e8d65e8b07f08a5d58')
+sha256sums_aarch64=('8c91f11c9a70d1ac8fd277dbf851d7e5e5daa02fd43edd442fce6e5ff301fe1d')
prepare() {
mkdir -p brave