Comment
This change only bumps brave-bin from 1.95.102 to 1.95.104 and updates the corresponding SHA-256 checksums for the upstream release archives. The source URLs remain HTTPS GitHub release links, there are no new build-time commands, no install-script changes, and no evidence of added persistence, privilege escalation, or network-fetch behavior beyond the declared sources. Based on the diff shown, this is a routine version/checksum refresh with low security risk.
@@ -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=('c5be7c420d3f256d63335464d8f689f5d4868791ff59db136dacaa70492ab53f')
-sha256sums_aarch64=('f58f081779a8b13f2a7c5e75f71a7a24fc465023b2e8274b727b48193b6462eb')
+sha256sums_x86_64=('1d2a6fc3e32ad7b62bb2aeae6d1ba4ba01acbec12a8a7a8310ea6ae1293816cc')
+sha256sums_aarch64=('9f2dab1cd328cdaa88302be319bd269d59a8a84c8dfc6ccaa71287b8c0629ac2')
prepare() {
mkdir -p brave