I'm getting this error when upgrading:

==> ERROR: One or more files did not pass the validity check!

I checked the checksums, and indeed, they don't match:

$ grep -A1 sha256 PKGBUILD 
sha256sums=('cd9facd9269ecb9eae4f513e6c7f9766e928d40064ae6e83841bdf6083cd0eb5'
            'a8622b5584d5458b608096f24ab2e52e40f1970baaf4e4cd1ffd69b64d149828')

This is the checksum of the actual source file:

$ sha256sum usbimager-1.0.10.tar.gz 
582a4121bec523c5f737d4c91a5a96357243c146330d7785ab54aa3730fba4ff  usbimager-1.0.10.tar.gz

I downloaded the source file here: https://gitlab.com/bztsrc/usbimager/-/releases

And it has that same checksum:

$ cd ~/Downloads
$ sha256sum usbimager-1.0.10.tar.gz 
582a4121bec523c5f737d4c91a5a96357243c146330d7785ab54aa3730fba4ff  usbimager-1.0.10.tar.gz

Am I doing something wrong here?

The 1.0.10-1 version failed to build for me due to a conflict between the gcc optimization level and FORTIFY_SOURCE:

==> Making package: usbimager 1.0.10-1 (Tue 10 Oct 2023 06:03:19 AM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading usbimager-1.0.10.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1959k    0 1959k    0     0  2314k      0 --:--:-- --:--:-- --:--:-- 2313k
  -> Found makefile.patch
==> Validating source files with sha256sums...
    usbimager-1.0.10.tar.gz ... Passed
    makefile.patch ... Passed
==> Extracting sources...
  -> Extracting usbimager-1.0.10.tar.gz with bsdtar
==> Starting prepare()...
patching file src/Makefile
Hunk #1 succeeded at 197 (offset 40 lines).
==> Starting build()...
make: Entering directory '/pjob.data/scratch/usbimager/src/usbimager-1.0.10/src'
make[1]: Entering directory '/pjob.data/scratch/usbimager/src/usbimager-1.0.10/src/bzip2'
gcc  -c blocksort.c
gcc  -c huffman.c
gcc  -c crctable.c
make[1]: Entering directory '/pjob.data/scratch/usbimager/src/usbimager-1.0.10/src/xz'
gcc -std=gnu89 -I. -DXZ_DEC_X86 -DXZ_DEC_POWERPC -DXZ_DEC_IA64 -DXZ_DEC_ARM -DXZ_DEC_ARMTHUMB -DXZ_DEC_SPARC -DXZ_DEC_ANY_CHECK  -c -o xz_crc32.o xz_crc32.c
make[1]: Entering directory '/pjob.data/scratch/usbimager/src/usbimager-1.0.10/src/zstd'
Using ar
Checking for x86_64-pc-linux-gnu-gcc...
gcc  -c randtable.c
cc  -D_FORTIFY_SOURCE=2 -DXXH_NAMESPACE=ZSTD_ -DZSTD_LEGACY_SUPPORT=0  -c -o common/debug.o common/debug.c
cc  -D_FORTIFY_SOURCE=2 -DXXH_NAMESPACE=ZSTD_ -DZSTD_LEGACY_SUPPORT=0  -c -o common/entropy_common.o common/entropy_common.c
gcc  -c decompress.c
In file included from /usr/include/bits/libc-header-start.h:33,
                 from /usr/include/limits.h:26,
                 from /usr/lib/gcc/x86_64-pc-linux-gnu/13.2.1/include/limits.h:205,
                 from /usr/lib/gcc/x86_64-pc-linux-gnu/13.2.1/include/syslimits.h:7,
                 from /usr/lib/gcc/x86_64-pc-linux-gnu/13.2.1/include/limits.h:34,
                 from common/zstd_deps.h:27,
                 from common/mem.h:24,
                 from common/entropy_common.c:18:
/usr/include/features.h:414:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
  414 | #  warning _FORTIFY_SOURCE requires compiling with optimization (-O)
      |    ^~~~~~~
...

As a quick workaround I added a small patch to my local build:

diff --git a/PKGBUILD b/PKGBUILD
index fdd57f3..5c73acb 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -21,7 +21,7 @@ prepare() {
 }

 build() {
-  USE_LIBUI=yes USE_UDISKS2=yes make -C "${pkgname}-${pkgver}/src"
+  CFLAGS="-O" USE_LIBUI=yes USE_UDISKS2=yes make -C "${pkgname}-${pkgver}/src"
 }

 package() {

Usbimager is available for armhf as well (in the GitLab page). Could you add support for armhf and aarch64?