starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #4978] [feature]: Add a settings toggle to disable automatic updates for your desktop app #1888

New issue

Closed

opened 2026-03-16 22:16:18 +03:00 by kerem · 7 comments

kerem commented

2026-03-16 22:16:18 +03:00

Owner

Originally created by @stevencorrea-chicago on GitHub (Apr 9, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4978

Originally assigned to: @CuriousCorrelation on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Summary

Toggle requested to disable automatic updates.

Why should this be worked on?

I work for a Fortune 500 company which has VM's available for contractors to use. In order to make software available to those contractors using VMs, the applications need to be virtualized. The problem is that specific versions are approved because applications are vetted on a version-by-version basis. If automatic updates are enabled and a new version is automatically installed, even for very minor functionality, new requests would need to be submitted to have the new version vetted. To bypass this annoyance, I'd like to request to have a toggle added in the settings of the application.

Originally created by @stevencorrea-chicago on GitHub (Apr 9, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4978 Originally assigned to: @CuriousCorrelation on GitHub. ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Toggle requested to disable automatic updates. ### Why should this be worked on? I work for a Fortune 500 company which has VM's available for contractors to use. In order to make software available to those contractors using VMs, the applications need to be virtualized. The problem is that specific versions are approved because applications are vetted on a version-by-version basis. If automatic updates are enabled and a new version is automatically installed, even for very minor functionality, new requests would need to be submitted to have the new version vetted. To bypass this annoyance, I'd like to request to have a toggle added in the settings of the application.

kerem

2026-03-16 22:16:18 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 22:16:34 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 10, 2025):

Hi @stevencorrea-chicago, thanks for your feature request. Just to clarify something - the Hoppscotch desktop app shouldn't install updates automatically. When updates are available, it should show a prompt where you can choose to "Install Update" or select "Later" (which skips the check and installation temporarily).

Could you clarify if you are looking disable the update check and prevent the prompt from appearing at all? Or is the "Later" option not working as expected in your environment?

The context would help in implementing the right solution for your use case.

@CuriousCorrelation commented on GitHub (Apr 10, 2025): Hi @stevencorrea-chicago, thanks for your feature request. Just to clarify something - the Hoppscotch desktop app shouldn't install updates automatically. When updates are available, it should show a prompt where you can choose to "Install Update" or select "Later" (which skips the check and installation temporarily). Could you clarify if you are looking disable the update check and prevent the prompt from appearing at all? Or is the "Later" option not working as expected in your environment? The context would help in implementing the right solution for your use case.

kerem commented

2026-03-16 22:16:39 +03:00

Author

Owner

@stevencorrea-chicago commented on GitHub (Apr 10, 2025):

In our case, we would need the update check completely disabled so the user
is never presented with an option to upgrade.

With respect to my employer, applications used within VM’s must be
approved on a version-by-version basis which is why automatic updates
cannot be allowed.

Thank you!

On Thu, Apr 10, 2025 at 1:09 AM Shreyas @.***> wrote:

Hi @stevencorrea-chicago https://github.com/stevencorrea-chicago,
thanks for your feature request. Just to clarify something - the Hoppscotch
desktop app shouldn't install updates automatically. When updates are
available, it should show a prompt where you can choose to "Install Update"
or select "Later" (which skips the check and installation temporarily).

Could you clarify if you are looking disable the update check and prevent
the prompt from appearing at all? Or is the "Later" option not working as
expected in your environment?

The context would help in implementing the right solution for your use
case.

—
Reply to this email directly, view it on GitHub
https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2791655383,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJV2PIVCFRYOQULDIAS55KL2YYDHZAVCNFSM6AAAAAB2Z6RJUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJRGY2TKMZYGM
.
You are receiving this because you were mentioned.Message ID:
@.***>
CuriousCorrelation left a comment (hoppscotch/hoppscotch#4978)
https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2791655383

Hi @stevencorrea-chicago https://github.com/stevencorrea-chicago,
thanks for your feature request. Just to clarify something - the Hoppscotch
desktop app shouldn't install updates automatically. When updates are
available, it should show a prompt where you can choose to "Install Update"
or select "Later" (which skips the check and installation temporarily).

Could you clarify if you are looking disable the update check and prevent
the prompt from appearing at all? Or is the "Later" option not working as
expected in your environment?

The context would help in implementing the right solution for your use
case.

—
Reply to this email directly, view it on GitHub
https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2791655383,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJV2PIVCFRYOQULDIAS55KL2YYDHZAVCNFSM6AAAAAB2Z6RJUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJRGY2TKMZYGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@stevencorrea-chicago commented on GitHub (Apr 10, 2025): In our case, we would need the update check completely disabled so the user is never presented with an option to upgrade. With respect to my employer, applications used within VM’s must be approved on a version-by-version basis which is why automatic updates cannot be allowed. Thank you! On Thu, Apr 10, 2025 at 1:09 AM Shreyas ***@***.***> wrote: > Hi @stevencorrea-chicago <https://github.com/stevencorrea-chicago>, > thanks for your feature request. Just to clarify something - the Hoppscotch > desktop app shouldn't install updates automatically. When updates are > available, it should show a prompt where you can choose to "Install Update" > or select "Later" (which skips the check and installation temporarily). > > Could you clarify if you are looking disable the update check and prevent > the prompt from appearing at all? Or is the "Later" option not working as > expected in your environment? > > The context would help in implementing the right solution for your use > case. > > — > Reply to this email directly, view it on GitHub > <https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2791655383>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AJV2PIVCFRYOQULDIAS55KL2YYDHZAVCNFSM6AAAAAB2Z6RJUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJRGY2TKMZYGM> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > *CuriousCorrelation* left a comment (hoppscotch/hoppscotch#4978) > <https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2791655383> > > Hi @stevencorrea-chicago <https://github.com/stevencorrea-chicago>, > thanks for your feature request. Just to clarify something - the Hoppscotch > desktop app shouldn't install updates automatically. When updates are > available, it should show a prompt where you can choose to "Install Update" > or select "Later" (which skips the check and installation temporarily). > > Could you clarify if you are looking disable the update check and prevent > the prompt from appearing at all? Or is the "Later" option not working as > expected in your environment? > > The context would help in implementing the right solution for your use > case. > > — > Reply to this email directly, view it on GitHub > <https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2791655383>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AJV2PIVCFRYOQULDIAS55KL2YYDHZAVCNFSM6AAAAAB2Z6RJUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJRGY2TKMZYGM> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

kerem commented

2026-03-16 22:16:44 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 10, 2025):

Ah I understand what you meant now. This is something I can definitely take a look into, although upon reflection, I think a much more elegant solution would be a standalone/portable version of the desktop app.

Portable applications typically don't include update mechanisms, as that's one of their base design principles. Key benefits being self-contained without modifying the system or automatically updating.

For an enterprise environment, a portable version would eliminate the update prompts entirely, and while I don't have the full context here, I believe this could perhaps improve the virtualization + distribution mechanics that you mentioned.

I could also look into implementing a toggle to disable updates, though this approach might still require some administrative oversight across installations and has a chance to potentially be reset during operations.

Both approaches are certainly possible to implement. I'd be interested in your thoughts on which solution would better serve your enterprise requirements.

@CuriousCorrelation commented on GitHub (Apr 10, 2025): Ah I understand what you meant now. This is something I can definitely take a look into, although upon reflection, I think a much more elegant solution would be a standalone/portable version of the desktop app. Portable applications typically don't include update mechanisms, as that's one of their base design principles. Key benefits being self-contained without modifying the system or automatically updating. For an enterprise environment, a portable version would eliminate the update prompts entirely, and while I don't have the full context here, I believe this could perhaps improve the virtualization + distribution mechanics that you mentioned. I could also look into implementing a toggle to disable updates, though this approach might still require some administrative oversight across installations and has a chance to potentially be reset during operations. Both approaches are certainly possible to implement. I'd be interested in your thoughts on which solution would better serve your enterprise requirements.

kerem commented

2026-03-16 22:16:49 +03:00

Author

Owner

@stevencorrea-chicago commented on GitHub (Apr 13, 2025):

I agree that a standalone version would be best suited for enterprise
environments that have to evaluate versions of applications on a
version-by-version basis. My vote is for the standalone app, but would you
hist the standalone versions in your site, GitHub or expect the end user to
compile it themselves?

On Thu, Apr 10, 2025 at 8:38 AM Shreyas @.***> wrote:

Ah I understand what you meant now. This is something I can definitely
take a look into, although upon reflection, I think a much more elegant
solution would be a standalone/portable version of the desktop app.

Portable applications typically don't include update mechanisms, as that's
one of their base design principles. Key benefits being self-contained
without modifying the system or automatically updating.

For an enterprise environment, a portable version I believe would
eliminate the update prompts entirely, and while I don't have the full
context here, I believe this could perhaps improve the virtualization +
distribution mechanics that you mentioned.

I could also look into implementing a toggle to disable updates, though
this approach might still require some administrative oversight across
installations and has a chance to potentially be reset during operations.

Both approaches are certainly possible to implement. I'd be interested in
your thoughts on which solution would better serve your enterprise
requirements.

—
Reply to this email directly, view it on GitHub
https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2793115481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJV2PIRAYVO6OZJGCYZSWO32YZX5XAVCNFSM6AAAAAB2Z6RJUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJTGEYTKNBYGE
.
You are receiving this because you were mentioned.Message ID:
@.***>
CuriousCorrelation left a comment (hoppscotch/hoppscotch#4978)
https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2793115481

Ah I understand what you meant now. This is something I can definitely
take a look into, although upon reflection, I think a much more elegant
solution would be a standalone/portable version of the desktop app.

Portable applications typically don't include update mechanisms, as that's
one of their base design principles. Key benefits being self-contained
without modifying the system or automatically updating.

For an enterprise environment, a portable version I believe would
eliminate the update prompts entirely, and while I don't have the full
context here, I believe this could perhaps improve the virtualization +
distribution mechanics that you mentioned.

I could also look into implementing a toggle to disable updates, though
this approach might still require some administrative oversight across
installations and has a chance to potentially be reset during operations.

Both approaches are certainly possible to implement. I'd be interested in
your thoughts on which solution would better serve your enterprise
requirements.

—
Reply to this email directly, view it on GitHub
https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2793115481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJV2PIRAYVO6OZJGCYZSWO32YZX5XAVCNFSM6AAAAAB2Z6RJUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJTGEYTKNBYGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@stevencorrea-chicago commented on GitHub (Apr 13, 2025): I agree that a standalone version would be best suited for enterprise environments that have to evaluate versions of applications on a version-by-version basis. My vote is for the standalone app, but would you hist the standalone versions in your site, GitHub or expect the end user to compile it themselves? On Thu, Apr 10, 2025 at 8:38 AM Shreyas ***@***.***> wrote: > Ah I understand what you meant now. This is something I can definitely > take a look into, although upon reflection, I think a much more elegant > solution would be a standalone/portable version of the desktop app. > > Portable applications typically don't include update mechanisms, as that's > one of their base design principles. Key benefits being self-contained > without modifying the system or automatically updating. > > For an enterprise environment, a portable version I believe would > eliminate the update prompts entirely, and while I don't have the full > context here, I believe this could perhaps improve the virtualization + > distribution mechanics that you mentioned. > > I could also look into implementing a toggle to disable updates, though > this approach might still require some administrative oversight across > installations and has a chance to potentially be reset during operations. > > Both approaches are certainly possible to implement. I'd be interested in > your thoughts on which solution would better serve your enterprise > requirements. > > — > Reply to this email directly, view it on GitHub > <https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2793115481>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AJV2PIRAYVO6OZJGCYZSWO32YZX5XAVCNFSM6AAAAAB2Z6RJUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJTGEYTKNBYGE> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > *CuriousCorrelation* left a comment (hoppscotch/hoppscotch#4978) > <https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2793115481> > > Ah I understand what you meant now. This is something I can definitely > take a look into, although upon reflection, I think a much more elegant > solution would be a standalone/portable version of the desktop app. > > Portable applications typically don't include update mechanisms, as that's > one of their base design principles. Key benefits being self-contained > without modifying the system or automatically updating. > > For an enterprise environment, a portable version I believe would > eliminate the update prompts entirely, and while I don't have the full > context here, I believe this could perhaps improve the virtualization + > distribution mechanics that you mentioned. > > I could also look into implementing a toggle to disable updates, though > this approach might still require some administrative oversight across > installations and has a chance to potentially be reset during operations. > > Both approaches are certainly possible to implement. I'd be interested in > your thoughts on which solution would better serve your enterprise > requirements. > > — > Reply to this email directly, view it on GitHub > <https://github.com/hoppscotch/hoppscotch/issues/4978#issuecomment-2793115481>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AJV2PIRAYVO6OZJGCYZSWO32YZX5XAVCNFSM6AAAAAB2Z6RJUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJTGEYTKNBYGE> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

kerem commented

2026-03-16 22:16:54 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 14, 2025):

Thanks for the feedback. I'll move the standalone version of the desktop app up in the feature priority list.

As for hosting, the standalone app will be hosted in desktop app release repository.

Users will be able to download the portable .exe (or .zip) directly without needing to compile anything themselves.

The repo will also maintain previous versions in the releases section so your team can control exactly which version is deployed in your VMs.

@CuriousCorrelation commented on GitHub (Apr 14, 2025): Thanks for the feedback. I'll move the standalone version of the desktop app up in the feature priority list. As for hosting, the standalone app will be hosted in [desktop app release repository](https://github.com/hoppscotch/releases/). Users will be able to download the portable `.exe` (or `.zip`) directly without needing to compile anything themselves. The repo will also maintain previous versions in the releases section so your team can control exactly which version is deployed in your VMs.

kerem commented

2026-03-16 22:16:59 +03:00

Author

Owner

@KaKi87 commented on GitHub (Jun 6, 2025):

Hi,

I would also like to suggest completely hiding the updater in the DEB version so that there's no temptation to try in-app updates that cannot work at all.

Thanks

@KaKi87 commented on GitHub (Jun 6, 2025): Hi, I would also like to suggest completely hiding the updater in the DEB version so that there's no temptation to try in-app updates that cannot work at all. Thanks

kerem commented

2026-03-16 22:17:04 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Nov 27, 2025):

This has been implemented via #5421 with the portable version of Hoppscotch Desktop, now available for Windows from v25.11.0-0.

Features for enterprise envs:

Configurable update notifications (can be disabled entirely on first launch)
Self-contained installation that doesn't modify system directories
All data stored in the application directory (portable between systems)
Previous versions remain available in the releases repository
Update notifications are separated from installation, allowing notification-only mode

This addresses the enterprise VM use case where version approval is required and automatic updates cannot be allowed.

For Linux package manager installations (.deb):

The infrastructure built for portable mode (separating notifications from installation) now makes it possible to apply the same notification-only behavior to .deb installations. This is tracked in https://github.com/hoppscotch/hoppscotch/issues/5623.

Closing as implemented.

@CuriousCorrelation commented on GitHub (Nov 27, 2025): This has been implemented via #5421 with the portable version of Hoppscotch Desktop, now available for Windows from [v25.11.0-0](https://github.com/hoppscotch/releases/releases/tag/v25.11.0-0). **Features for enterprise envs:** - Configurable update notifications (can be disabled entirely on first launch) - Self-contained installation that doesn't modify system directories - All data stored in the application directory (portable between systems) - Previous versions remain available in the releases repository - Update notifications are separated from installation, allowing notification-only mode This addresses the enterprise VM use case where version approval is required and automatic updates cannot be allowed. For Linux package manager installations (.deb): The infrastructure built for portable mode (separating notifications from installation) now makes it possible to apply the same notification-only behavior to .deb installations. This is tracked in https://github.com/hoppscotch/hoppscotch/issues/5623. Closing as implemented.

kerem referenced this issue

2026-03-17 01:09:13 +03:00

[PR #1888] [MERGED] Feature: Adds arrow keys navigation on power search #3549