usebruno
[Feature Request] Auto updater
Hello,
I'd like to request an auto updater feature, a lot of releases I can't follow them all.
Sure. Just got Signing and Notarizing MacOS builds completed. Next stop is to sign Windows build, after that I will work on implementing auto updater.
Also curious if there are any updates regarding this. Thanks, @helloanoop!
I would love to work on this feature. Just curious about what we will be using.
What will we be using?
- update.electronjs.org which will require us to release bruno to electron showcase
- Github release. hazel or vercel
As I have seen we are using vercel for the deployment this might be a good choice to use with the release.
Please let me know and I will be working on the PR
Another option is to install Bruno via brew and periodically run brew upgrade brew.
Any automated update process should be configurable to ensure that users generally or admins of managed devices can manage the update process for their users.
Not all users may be familiar with or authorised to use brew for installation or updates.
We are working on this in our current sprint. This is expected to go out Dec first week.
Hi, we've released auto updater feature in 1.36.0. Those who were on 1.36.0 might have seen it in action when we released 1.36.1. We're working on a feature to disable it when needed. This will likely go out in the upcoming release!
Hi, we've released auto updater feature in 1.36.0. Those who were on 1.36.0 might have seen it in action when we released 1.36.1. We're working on a feature to disable it when needed. This will likely go out in the upcoming release!
Any update, where it has been implemented and documented?
Hi, we've released this feature in our 1.37 release. Please refer to the image below. Thanks!
Hi, I've found this issue from this other issue but I though this would be the most appropriate place to mention this.
The first time I saw this dialog out of the blue I though it may be some kind of malware. I mean, an application trying to install with dpkg an unsolicited package without any previous warning is really bad from the security perspective.
Please, consider adding a more user-friendly dialog before showing the "authenticate as root for this command" dialog informing the user that the application is going to try to update itself and root authentication may be required, maybe with a "don't show this warning again" checkbox, to mitigate this impression.
OTOH, if non-Debian Linux distributions can be skipped from this process would be great, given that the auto update process is going to fail anyway.
Just my 2¢
@Terseus ran into this today for the first time, part of this is just how electron-builder functions. Not sure if there's a way to control when the updater attempts to apply, but it might be nice to either prevent the app from fully closing if an update is downloaded (give a message to the user asking if they wish to update) or change the flow for updating entirely if possible.
Having a post-close script trigger a sudo attempt to run bash to do the update tends to give bad feelings.
Hi, we understand your concern. we're planning to introduce a dialog which will prompt user when quitting the app to install rather than forcefully installing on quit. What do you think?
Closing this issue since we have implemented Auto Updater.
I have created #4128 to track improvements related to prompting user before attempting an update, informing them that root authentication may be required.