Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Auto updater #103

Open
snake302 opened this issue Feb 22, 2023 · 7 comments
Open

[Feature Request] Auto updater #103

snake302 opened this issue Feb 22, 2023 · 7 comments
Assignees
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Milestone

Comments

@snake302
Copy link

Hello,

I'd like to request an auto updater feature, a lot of releases I can't follow them all.

@helloanoop
Copy link
Contributor

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.

@helloanoop helloanoop added good first issue Good for newcomers help wanted Extra attention is needed labels Feb 22, 2023
@helloanoop helloanoop added this to the v1 milestone Oct 5, 2023
@LouisLecouturier
Copy link

Any updates on this ?

@junguye-BRONGA
Copy link

Also curious if there are any updates regarding this. Thanks, @helloanoop!

@sethstha
Copy link
Contributor

sethstha commented Dec 3, 2023

I would love to work on this feature. Just curious about what we will be using.

What will we be using?

  1. update.electronjs.org which will require us to release bruno to electron showcase
  2. 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

@jwetzell
Copy link
Contributor

This shouldn't be that bad using the GitHub releases and this.

@jwetzell jwetzell mentioned this issue Jul 31, 2024
1 task
@chimit
Copy link

chimit commented Aug 2, 2024

Another option is to install Bruno via brew and periodically run brew upgrade brew.

@built2order
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

9 participants