Summary of the new feature / enhancement
As soon as a new release is made, PowerShell will display a message like:
A new PowerShell stable release is available: v7.5.4
Upgrade now, or check out the release page at:
https://aka.ms/PowerShell-Release?tag=v7.5.4
The 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.
This resulted in this bug report discussion: #26261
Where it became apparent that this non-urgent and non-actionable alert has been annoying quite a few people.
I have not looked at the code for this, but this is what I would like to see:
Wait 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.
There 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.
Summary of the new feature / enhancement
As soon as a new release is made, PowerShell will display a message like:
The 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.
This resulted in this bug report discussion: #26261
Where it became apparent that this non-urgent and non-actionable alert has been annoying quite a few people.
I have not looked at the code for this, but this is what I would like to see:
Wait 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.
There 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.