René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Only show 'new stable release available' notification a week after the current version is stale.","articleBody":"### Summary of the new feature / enhancement\n\nAs soon as a new release is made, PowerShell will display a message like:\n\n```\nA new PowerShell stable release is available: v7.5.4\nUpgrade now, or check out the release page at:\nhttps://aka.ms/PowerShell-Release?tag=v7.5.4\n```\n\nThe problem is, for the various distribution methods that people use, it's very likely that the release is not yet available; or that in the course of natural operation, they would get the upgrade anyway. If I use Windows Update (e.g. via WSUS or direct), winget, brew, apt, yum, etc; these all take a short while to come through. Therefore, the new version warning is often not even actionable. \n\nThis resulted in this bug report discussion: https://github.com/PowerShell/PowerShell/issues/26261\n\nWhere it became apparent that this non-urgent and non-actionable alert has been annoying quite a few people. \n\nI have not looked at the code for this, but this is what I would like to see: \n\nWait a reasonable amount, until the current version is \"reasonably stale\". This can have a hard-coded default of (for example) a week, or it can be overridden in a setting somewhere. Once the installed version is stale enough, then display the warning.\n\nThere may need to be the ability to override this in case of an urgent security alert; but if you don't do that, you can probably make it async/cached... so there may be some performance/latency benefits too.","author":{"url":"https://github.com/alirobe","@type":"Person","name":"alirobe"},"datePublished":"2025-10-22T23:54:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/26284/PowerShell/issues/26284"}