Comment
The change only updates the Brave binary package version and refreshes the SHA-256 checksums for the upstream release archives. No build logic, install scripts, permissions, dependencies, or source URLs were altered. The sources remain HTTPS GitHub release artifacts from the official Brave repository, and the package still uses pinned release URLs. I do not see any new supply-chain, persistence, or privilege-escalation risk introduced by this diff.
@@ -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=('d30e9e1206074c0f24ad0eca1ca44b9a3abcde05a837074ec9045c8e599b6733')
-sha256sums_aarch64=('324df5dd35fea33f09410af9ea6cf7775ace25af90e745a1da06c462e938b60a')
+sha256sums_x86_64=('c5be7c420d3f256d63335464d8f689f5d4868791ff59db136dacaa70492ab53f')
+sha256sums_aarch64=('f58f081779a8b13f2a7c5e75f71a7a24fc465023b2e8274b727b48193b6462eb')
prepare() {
mkdir -p brave