AdmiringWorm
commented
1 year ago Before we are able to start triaging this issue, we'll need you to first fill out the template that we have in place for the repository.
Additionally, is this request for Chocolatey CLI (Open Source), or for Chocolatey Licensed Extension?
For reference, the following is the template that needs to be filled out:
All sections/headers are mandatory to be filled out, or use the content N/A
<!--
Ensure you have read over [Submitting Issues](https://github.com/chocolatey/.github/blob/main/SUBMITTING-ISSUES.md)
Please check to see if your issue already exists with a quick search of the issues. Start with one relevant term and then add if you get too many results.
NOTE: Keep in mind we have a [Code Of Conduct](https://github.com/chocolatey/.github/blob/main/CODE_OF_CONDUCT.md) that we expect folks to observe when they are looking for support in the Chocolatey community.
Name your issue appropriately: give it a sentence that reads well enough for anyone seeing this in the release notes to what it is.
When writing out the issue details please ensure you are writing it as if you were explaining it to somebody else.
Even if you will be working on and resolving the issue yourself. This helps others to understand the reasons for the issue and for it to be searchable in future.
Please do not remove any of the headings.
If a heading is not applicable then enter N/A: Why it's not applicable
Please remove all comments before submitting.
-->
## Is Your Feature Request Related To A Problem? Please describe.
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
## Describe The Solution. Why is it needed?
<!-- A clear and concise description of what you want to happen. -->
## Additional Context.
<!-- Add any other context or screenshots about the feature request here. -->
## Related Issues
<!-- Enter and link any related issues here. If there are no issues, replace with N/A. -->
- Issue #
- Issue #
When upgrading packages the standard behaviour is to install the latest version. However, sometimes upgrades come with issues. For that reason some people choose to delay upgrading. Probably the most prominent example of this is corporations choosing to delay Windows Updates so they can test and see if Microsoft revokes or re-patches them.
It would be extremely handy to have an option in Chocolatey to limit upgrades to packages that were published at least X days previously, i.e. are at least X days old. If the package survives that long without an emergency update, it's probably okay.