Skip to content

Commit 8227a7c

Browse files
TravisEz13sdwheeler
authored andcommitted
document how fast you must update to the latest patch. (#4050)
1 parent c0f374b commit 8227a7c

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

reference/docs-conceptual/PowerShell-Support-Lifecycle.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,15 @@ once every six months (examples: 6.0, 6.1, 6.2, etc.)
3636
For example, if PowerShell Core 6.1 is released on July 1, 2018,
3737
you would be expected to update to PowerShell Core 6.1 by January 1, 2019 to maintain support.
3838

39+
> [!IMPORTANT]
40+
> You must update within 30 days after each new patch version release to continue receiving support.
41+
42+
For example, If you are running PowerShell Core 6.1 and 6.1.3 was released on February 19, 2019,
43+
you would be expected to update to PowerShell Core 6.1.3 by March 21, 2019,
44+
which is 30 days after the release to maintain support.
45+
If any fixes are found to be required,
46+
the fixes will be released in our next cumulative update.
47+
3948
![PowerShell Core branch lifecycle][lifecycle-chart]
4049

4150
The Modern Lifecycle Policy also requires that Microsoft give customers 12 months

0 commit comments

Comments
 (0)