Comment
The change only updates the SHA-256 checksum for the upstream release tarball in PKGBUILD. The source URL remains the official GitHub release over HTTPS, with no added build steps, scripts, patches, or packaging logic changes. I did not see any new integrity, execution, or persistence risks introduced by this diff alone. The main effect is to accept a different upstream tarball for the same version, which is normal when upstream re-rolls a release or the package was previously out of date, but by itself it does not indicate malicious behavior in the PKGBUILD change.
@@ -13,7 +13,7 @@ groups=('qownnotes')
depends=('qt6-base' 'qt6-svg' 'qt6-declarative' 'qt6-websockets' 'aspell' 'botan' 'libgit2' 'libsecret')
makedepends=('qt6-tools' 'cmake')
source=("https://github.com/pbek/QOwnNotes/releases/download/v${pkgver}/qownnotes-${pkgver}.tar.xz")
-sha256sums=('b2673e25378ad01b685eee9b89221eb47eae7eb53cbec862220e8a823deb86ec')
+sha256sums=('bcf25a722f7fdd8384b9450c85e5fc9708942244108b75ff57139df5ee671410')
prepare() {
cd "${pkgname}-${pkgver}"