It seems networkException forgot to bump the pkgrel of the github build, which then caused it to build the package with the wrong pkgrel.
The remote has tagged the released as -3 but the filename is -1, which is causing a conflict within the PKGBUILD.
Pinned Comments
networkException commented on 2022-09-20 17:36 (UTC)
Please note that normally it's not required to flag this package as out of date. I usually tag releases in the main ungoogled-chromium repository and update the arch packaging right afterwards.
If the package hasn't updated after an ungoogled-chromium release GitHub Actions might still be building or the ungoogled-chromium patchset got updated for non Linux platforms only to match their upstream release cycle