New to the community? Start here

[Automate] Configuration option in Automate to only update minor release versions

1

It would be awesome if there was a setting to skip major release versions. For example, if a plugin is going from 3.4.2 to 3.4.3, then go ahead and update it at the scheduled time. But if it is going from 3.4.2 to 4.0, skip it. Wait for 4.0.1

Major releases are more likely to break things, so I would only want to update those manually. Otherwise I want to wait for the inevitable fixes.

Thanks!

Wed, 1 Jun 2022 5:21:24
  • Nithin Ramdas
    • Support Wizard

    Hi frobroweb ,

    In general, it isn’t a good practice to skip updates. A major update can also have security patches or even a bug fix from the previous minor updates.

    There could be such factors which would vary from one site to another depending upon each plugin. Skipping the major release without considering the above can also lead to its own issues.

    Automate at the moment only have the option to disable updates for specific plugins and not based on versions as it can only bring more complexity to the update structure.

    However, I do understand you and our Automate team are already looking at implementing more features on how issues that might occur due to a plugin update could be reduced which would align with your concerns too.

    I’ll make sure to bring your request to our team’s attention so it would help on how these could be looked down the roadmap.

    Have a nice day ahead.

    Kind Regards,
    Nithin

  • James Farmer
    • Founder & Chair (honest)

    Hey frobroweb thanks for the request and for being a member of WPMU DEV :slight_smile:

    I get what you’re saying and we’ve all been there (big new release breaks loads of stuff so we wait till at least the .0.1 or .1 to upgrade but as Nithin says, given the frequency of security upgrades required in WP plugins allowing that kind of skip (or any kind of skip) would kind of defeat the purpose of Automate and we’d instead encourage you to use the “Safe Update” feature (have you tried it? It’s awesome, my spec too :smirk: lol) with backups and visual regression to let you know if there has been a problem.

    If you were really concerned about a particular plugin (or theme) you could just exclude it from Automate too and manage updates via The Hub (which does have an ignore updates feature… which is also awesome).

    Hope that helps?

    • Álvaro Novais
      • DEV MAN’s Sidekick

      Hello James Farmer ,

      and we’d instead encourage you to use the “Safe Update” feature (have you tried it? It’s awesome, my spec too :smirk: lol) with backups and visual regression to let you know if there has been a problem.

      To make sure I’m not missing anything, is this a feature of The Hub? If yes, where can I find it?

    • FroBro
      • Master of Hair and Interwebs

      Thanks for the response. Yes I do use the Safe Update feature. I would argue that skipping only major releases is less risky than excluding a plugin from updates altogether — that way it’s the best of both worlds. But I hear you, and I can respect that decision.
      Thanks for building an awesome platform! I’m looking forward to DNS registration whenever that gets rolled out.

    • Steve - Just Think BiG
      • Thinking Bigger

      Hi James,

      I understand where you’re coming from. I take daily backups of sites, so don’t specifically use the Safe Update feature in Automate but the outcome’s basically the same. However, I have WordPress configured not to install major updates for the same reason. As you rightly point out, major updates can couse all kinds of issues.

      For that reason, I’m with frobroweb and would +1 his request. I just like to anually update major changes where possible – just for peace of mind. Like him, I respect your decision but wouldstill welcome the facility, if it’s not too challenging to add in.

      Regards,

      Steve

  • Julian
    • Click Here

    I would use this feature on some plugins I don’t completely trust not to cause trouble. If there were the option to skip major versions, temporarily or until we update manually, that really wouldn’t hurt would it? Yes major version may contain bug and security fixes too which may be important, but they’re also more likely to break things… Automate’s safe updates are only partially useful here since what if a major updated causes an issue that isn’t immediately apparent? Or does not cause the front-end to visually change, which is what safe updates looks for?

    I don’t know. It would be a feature you’d have to use with consideration and at your own risk of course.