Option to disable auto updates

[Golgo1]

Describe the bug
Postman updates even when Auto updates are turned off

To Reproduce
Run a slightly older version of Postman
Postman will update, breaking critical functionality

Expected behavior
Don't update until directed to

Screenshots
If applicable, add screenshots to help explain your problem. Please make sure the screenshot does not contain any sensitive information such as API keys or access tokens.

App information (please complete the following information):

• App Type: Native App
• Postman Version: 7.2.2 forced to 7.3.4
• OS: Win 10

Additional context
Yes, this has been raised before and closed. This should not be ignored.

[preethammavin]

@Golgo1 let us know what is the critical functionality so that we can get it sorted for you. Postman enables updates being turned off for major versions as we expect that it might break user workflows.
Where as minor versions only include updates to current system to ensure we continuously improve the product without breaking user workflows by pushing incremental feature updates, bug fixes and security bumps. We treat regressions as an unacceptable class of bugs at Postman and we strive to ensure it does not happen, please do let us know what are functionalities that you feel are broken in the release and we shall ensure that it is fixed.

[Golgo1]

Thank you for the reply. The primary bug relates to SSL connections. I've created bug 7000 to address that.
I've noticed a few other GUI-related bugs as well. In fact that's how I knew I was updated. (I'll make separate reports for those)
I was force updated a month ago to 7.3.3.. BEFORE it was released on the website. The Latest was still 7.2.2.
7.3.3 broke many of the same features, but I was able to re-install 7.2.2 and work for a few weeks.
7.3.4 is force updating instantly.

I appreciate the quick responses on both bug reports, but I need to spend my morning configuring a different tool so I can try and meet my project deadline
I know this is not the place for complaints, but I feel having the option to control their own updates is a feature the community desperately needs, and is being ignored

[UncleBravado]

I fully support that requests as many other users in comments to different tickets. I do not understand why to force update, especially if it is not about minor updates or patches (as you claim) - for instance with version 7.3.X there were significant updates with many regression bugs. I do not think that the complete change in component rendering request's response is a minor change. Postman is not a toy, it is a serious tool for many of us and we wasted a lot of time to revert the version, just to repeat this exercise with every restart.

Just imagine that it happens to your phone and it gets unusable every morning.

I appreciate your approach to regression bugs but it is just impossible to avoid them, so maybe better let the desperate users have the possibility to control the updates and do not ignore that request as your decision to force updates seems to be totally against Postman users.

[robross0606]

This is a huge problem with your design that needs to be addressed ASAP. Updates need to be able to be shut off COMPLETELY. Frankly, no one cares what you classify as a "minor" vs "major" upgrade. People turn off updates because they need consistent repeatable behavior, want to limit network usage, and more. Many people need a tool that's not going to change out from underneath them at any time, regardless of whether the developer thinks (often incorrectly) that this is a "minor" change. This is also a red flag security risk for places where version control is critical and software is tracked.

[robross0606]

Perhaps "major" updates should be considered anything that isn't a third level point release? How is the move from 7.2 to 7.5 not considered a "major" release? Look at the change log! Just the update to 7.3 has a massive number of potentially breaking changes. A whole OS architecture support was removed and a completely new (and not thoroughly tested) richtext editor was swapped in. Massive fail.