Repository navigation
Option to disable auto updates #6999
Description
Activity
@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.Reacted by Neya, iniklyaev, L Daniel, Tom Thorogood (Aligent) and m-gordon-neworangeThank 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 ignoredI 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.
Reacted by robross0606, Akbar Ahmadi, prdemelof, Oluwasoji Ojo, alexj-novisto, 黄连木笛, Rexee, Alexandru Rosianu, Arifia Kasastra R, A Yashwanth and 13 moreThis 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.
Reacted by Seu Pedro, robert, Dan, prdemelof, Aravind Parappil, Juho Vainio, alexj-novisto, 黄连木笛, KJ Kim, Rukko and 25 morePerhaps "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.
Would like to point out updates are a pain, as one is not able to save custom setting for fonts and colors. Asking on the forums a person showed how to de-compile the resource file, after which I then fix up the css files to get the fonts and colors desired. I'm not doing this to make it look nice, i'm doing it so I can simply use Postman. Thought after setting "Disable automatic updates" would fix is. Seems wrong for two reasons. First it seems backwards, minor updates should be just that, minor. Secondly where is the prompt to allow a person to opt out if the update will be forced on them? Finally there should be an option if there is a critical security issue, ah but that we can all agree a security fix would not be a minor issue... But simply adding minor spacing or "minor" updates, should be completely optional if a user doesn't want the update.
@ Postman guys: Why are you insisting to force us to update, even on minor updates?
This is no way to win new users! And you might lose existing ones.
We simply don't want automatically minor updates! Is it so hard to understand it?
We are not some mobile-app-freaks who just want to have the latest thing.
Just let us decide if and when we want minor updates!
This is really annoying!
Stop forcing us to update! Should be our decision!Reacted by Ranga C, m12lrpv, Alexandru Rosianu, Gourab Sarkar, A Yashwanth, Samuel Oliveira, heron1, Haris F., Kaung Khant Kyaw, Dylan Schlabach and 8 more@stefanluchian As mentioned by @preethammavin above, minor updates should not break your workflows, and are here to make sure you have the latest security updates and bug fixes.
You can disable major updates in your app settings, and if you'd like to stay on v7 for now please reach out to help@postman.com and they'll help you revert to it.
P.S: I've removed your comment from the other issues as this is was the same one copied/pasted and these issues were closed.
Reacted by Alexandru Rosianu, Gourab Sarkar, Keshav, Nxys, Arifia Kasastra R, Bassel Cheaib, A Yashwanth, Samuel Oliveira, kho-Co, Ajetunmobi Isaac and 16 moreReacted by Zerogoki00 and Andrew Fedyanin@arlemi I agree that minor updates should not break user workflows and they provide users with the latest security updates and bug fixes, it is really useful. But this applies not only to the Postman app, it applies to every software we use, it doesn't care if it is a simple calculator or an entire operating system. Following your comment all software must force users to update, and it doesn't happen. Users should have the ability to decide (People over tools).
I dislike when the updates are forced because they can have a significant impact over metered connection and minor updates should not break anything but we are humans we can make mistakes, it is because security and bug issues exist. You can discontinue the old version if you like, I'd rather it stop working than not being able to decide.
If you implement this, users who use automatic updates will not be affected. i don't see a good reason to not implement it.
The arrogance of these statements is that the word "should" keeps being thrown around. The fact is, we're all human. Humans make mistakes. People should have the right to stick with a particular version that they know is stable and update on their terms. Not when you deem it necessary and then accidentally push a breaking bug. We've already seen how this works out when you "fix" something and cause a bad regression bug on a minor update. How many of those instances have to happen before you listen to your users and allow us to STOP automatic updates, even for what you deem a "minor fix"?
Reacted by Juho Vainio, Alexandru Rosianu, Keshav, Arifia Kasastra R, A Yashwanth, Samuel Oliveira, heron1, Karthik, exetroncorp, Enrique Medina and 1 moreAgreed, most programs "SHOULD" allow users the ability to work as they desire. Programmers "SHOULD" remember they are the ones providing a service to what users need. Seems like such an easy solution here? "SHOULD" be a pretty simple question before updating... "SHOULD" ask "Would you like to update "Yes/No"? The program "SHOULD" honor a users choice and back out.
It seems like this "SHOULD" be a simple fix and all would be happy. What are we missing?
82 remaining items
I found the auto updates annoying, so found many other tools like "Thunder Client" which is a VS Code extension that works well for my needs, or Insomnia and imaging any number of other tools as a Postman replacement. Even started wrote a utility the i can read in a Postmand collection, hit a rest/swagger end point and build up the request myself to invoke the API calls. No reason to suffer with Postman... :)
Just a heads up - Insomnia already imports Postman without any extra work involved. Another option is you can export to
cURLand import it elsewhere too ascURLis pretty much standard on most of these apps.@postman-staff can we get a status update on this issue?
Reacted by Lajos MészárosStill dont understand why postman team is not giving us any update regarding the issue. This is really an annoying UX issue.
Reacted by Vadim Nikolaev, HakanKoseoglu, Neya, rufus20145, Andrew Pitukh and ProfessorDragonI've solved this temporarily by adding
127.0.0.1 dl.pstmn.ioto my hosts file.Reacted by rufus20145, Hamed, ProfessorDragon and sunglee42such non sense team. either their developers dont know how to ship backward compatible. or they are totaly arrogant fools.
Reacted by visory-kunal, HakanKoseoglu, Neya and fix-a-lotReacted by puz_zleAnother upvote for this feature, every time I open Postman it prompts for "An update is ready to install. Postman is trying to add a new helper tool. Enter an administrator's name and password to allow this.".
Except I can't as it's a corporate laptop with no administrator rights. Please allow us to disable this and auto updates.
Reacted by visory-kunal, HakanKoseoglu, Alexander Kiel, rufus20145, Kevin Clough, Hamed, Andrew Pitukh, YuriyStepanovSber and ProfessorDragonAdding my voice to the issue, 6 years later.
Reacted by Hamed and ProfessorDragonMadness. First, tell us CLEARLY what you are attempting to install. I'm not going to assign a 3rd party app admin rights just because you asked nicely. Helper tool? What helper tool, give specifics!
One day...
I find it also annoying to get constantly update popups from macOS almost every day, while only having Postman open in the background, not having used it since a week. This noice should end. Otherwise Postman is still a good tool.
Reacted by Hamed and fix-a-lotThis is very and very annoying. "An update is ready to install. Postman is trying to add a new helper tool." almost every day
Reacted by James Burr, ProfessorDragon and fix-a-lotIt has been nearly 7 years since this issue opened and the fact that it still is an issue is very disappointing. The workaround to just blacklist the urls in the host file in a product built by developers for developers is just crazy to me and very disappointing since we pay for so many enterprise licenses.
Reacted by fix-a-lot@rabih Enterprise users can use the Enterprise application and set a specific version of the app for the entire org. Please check the docs here: https://learning.postman.com/latest-v-12/docs/administration/enterprise/managing-enterprise-deployment
Unbelievable! There was a problem in 12.10 and I could not use Postman for a week or two, until 12.11 was released... No option to rollback, to disable updates, no solution but wait.
This is ridiculous.It's really frustrating that I have to reconfigure my firewall settings every time the patch version bumps up. I'd love to be able to update only occasionally, whenever I feel like it.
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):
Additional context
Yes, this has been raised before and closed. This should not be ignored.