Powershell lifecycle document still lists 7.6.6 as the latest LTS release

Open Beginner friendly
#13,391 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
powershell
Domain
documentation

Research direction

Start with the linked PowerShell support lifecycle page and locate where it identifies the latest LTS release. Check the current release information and the Brotli security concern mentioned in the issue, then update the lifecycle information or add a link to the changelog. Done when the page clearly identifies the current LTS release and points readers to authoritative release details.

Written by the indexing model from the issue text.

Description

issue-doc-bug needs-triage
Prerequisites
  • Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
  • Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Typo in Get-Foo cmdlet" instead of "Typo."
  • Verify Version: If there is a mismatch between documentation and the behavior on your system, ensure that the version you are using is the same as the documentation. Check this box if they match or the issue you are reporting is not version specific.
Links

https://learn.microsoft.com/en-us/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.6

Summary

The PowerShell support lifecycle document at https://learn.microsoft.com/en-us/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.6 still lists 7.6.6 as the latest LTS release.

This is misleading and dangerous, as (as I understand it - the documentation isn't very clear which is part of this issue) this version is still vulnerable to the Brotli security issue in .NET.

Details

No response

Suggested Fix

Have a process to keep this document up to date, or at least link to the actual changelog.

Dominant language
PowerShell
Stars
2.6k
Forks
1.7k
Avg merge
1d 4h
Merged PRs (30d)
4

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MicrosoftDocs/PowerShell-Docs

All issues in MicrosoftDocs/PowerShell-Docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.