block
Feature Request: Automatic Update Installation
Please explain the motivation behind the feature request.
Currently, when a new update is available, the app downloads the update to the Downloads folder. However, the user still needs to:
- Close the app manually.
- Go to the Downloads folder.
- Install the update manually.
This is a bit inconvenient and interrupts the workflow.
Describe the solution you'd like
It would be great if the app could:
- Automatically install the update after downloading.
- Restart itself without requiring the user to manually install the downloaded file.
Describe alternatives you've considered
use electron-updater, I see we already have it on the goose project and have autoupdater.ts too, maybe we need to enable autoUpdater.autoDownload = false; to true and make some additional changes to the file to automate the process
- [x] I have verified this does not duplicate an existing feature request
Some questions/comments @Abhijay007 wanted insights on @DOsinga @alexhancock @zanesq @michaelneale @jamadeo
They have a few questions about Goose's auto-update and extension distribution:
Are we intentionally preventing Goose from auto-downloading and restarting? Reported issue here, which appears similar to this related issue. What's the intended distribution method for Goose extensions?
I also noticed the Goose package isn't published to the npm registry. I came across it in @iandouglas' video https://www.youtube.com/shorts/QKg2Q6YCzdw where it looks structured like a Java package, distributed via Gradle or Maven. I couldn't find it published on either platform.
Thanks @taniashiba for posting this. This here is related to this issue: https://github.com/block/goose/issues/4304, which is closed as it was not a goose issue, but I think it was similar to what we resolved earlier
I also noticed the Goose package isn't published to the npm registry. I came across it in @iandouglas' video https://www.youtube.com/shorts/QKg2Q6YCzdw where it looks structured like a Java package, distributed via Gradle or Maven. I couldn't find it published on either platform.
There's no reason we can't do it, someone can definitely pick it up if they are interested. I think we gave it a quick try but ran into strange issues with it after it was packaged up and had to disable it to get a release out.
Hi @EbonyLouis , I’d like to work on this issue as my first contribution for Hacktoberfest. I have experience with Rust, JavaScript/TypeScript, React, and Node.js, and I’m excited to get started. Could you please guide me if there are any specific steps I should follow before beginning?
Couple things to keep in mind with this:
- Please test that it works in a built / distributed app not just on local
- We currently have support to hide automatic updates using the
UPDATES_ENABLEDflag please keep that functionality working.
OK sure sir @zanesq currently i am working on #4365 issue after that i will surely work on this
thanks
Thanks for taking this issue! Let us know if you have any questions!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @SanchitMahajan236, since @naveenkumar29052006 was asking to contribute to this first, I have reassigned this task to them. I encourage you to explore other issues in #4705 !
Hi @naveenkumar29052006 - wanted to check on your progress with this issue and see if you needed any help :)
Thanks for taking this issue! Let us know if you have any questions!
Posting here for everyone's reference - @AdemolaAri basically finished this for Hacktoberfest, but there was something on the our side from the dev team we had to look into in order to verify it and get it across the finish line. However, we will be getting his contribution approved once we are able! And I will for sure be rewarding @AdemolaAri credit in a different way outside of Hacktoberfest for all the hard work on it. ❤️ thank you!