@dct As you can see, checking for an update on 2.3.0 is saying it's up-to-date https://postimg.cc/ykFZhLWV
Also, the version being served on the https://proton.me/mail/bridge#download is 2.3.0 (deb and PKGBUILD) https://postimg.cc/pmC54yD4
More than that, the GitHub repo marked this release as a pre-release, so I consider 2.4.0 as a pre-release.
I don't know what you want me to do about the GitHub repo, it's not in my control, you can always open an issue there and ask about what's going on with the pre-release tag and versions on windows being updated to 2.4.0, you can also submit an AUR package called protonmail-bridge-pre-release or protonmail-bridge-beta or anything you want, anytime you want, please consider my concern not wanting to update immediately after a pre-release, introducing potential bugs, etc... It's not "failing" to update, it's a choice not to update to the latest commit/beta/pre-release
Pinned Comments
carsme commented on 2023-12-08 22:34 (UTC) (edited on 2023-12-08 22:35 (UTC) by carsme)
NOTICE: This pkgbase is now produces two packages:
protonmail-bridge-core
: Containing the core daemon & CLI program.protonmail-bridge
: Containing the Qt desktop application.The second package depends on the first. If you don't have a need for the desktop application, you can now choose to only install
protonmail-bridge-core
.This packaging change should be seamless and no action should be required before or after the upgrade.
Thanks to @ali.molaei and @BenTheTechGuy for the feedback regarding this change!
bthompson commented on 2021-06-17 04:13 (UTC)
Just having pass installed with a key set up wasn't enough for me, I had to follow this: https://pychao.com/2020/06/10/update-on-using-protonmail-bridge-on-headless-wordpress-linux-servers/