Hello Paulina, thanks for this plugin, I find it very useful!
I prefer to update packages after they have aged for a couple weeks before I update to the new version. Often when a package has a significant updated, one or more small bug-fix updates will follow soon after. My practice is to delay updating until the package has been in the wild for couple weeks so that I can avoid running into these early bugs.
Would it be possible for you to add an "aging" option to the version checker so that if the user has set an aging time period, the plugin wouldn't flag the package as needing an update until it the latest version had aged by the specified amount? So in addition to checking if "published version number" > "my version number", also check if "now datetime" > "published version datetime" + "aging time period". I would find this feature very helpful.
Thanks again!
Hello Paulina, thanks for this plugin, I find it very useful!
I prefer to update packages after they have aged for a couple weeks before I update to the new version. Often when a package has a significant updated, one or more small bug-fix updates will follow soon after. My practice is to delay updating until the package has been in the wild for couple weeks so that I can avoid running into these early bugs.
Would it be possible for you to add an "aging" option to the version checker so that if the user has set an aging time period, the plugin wouldn't flag the package as needing an update until it the latest version had aged by the specified amount? So in addition to checking if "published version number" > "my version number", also check if "now datetime" > "published version datetime" + "aging time period". I would find this feature very helpful.
Thanks again!