PowerShell / PowerShell/PowerShell

Stop nagging about "latest" when I'm on "latest LTS"

Open
#20,210 8 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Enhancement Needs-Triage
Dominant language
C#
Stars
55.5k
Forks
8.5k
Avg merge
1d 2h
Merged PRs (30d)
88

Description

Summary of the new feature / enhancement

As a developer stuck on LTS for compatibility with Microsoft's GitHub and Azure Pipeline agents, I don't want to be nagged about versions I'm not allowed to use.

I really do want to know when there's a new LTS release, but the current implementation means that every time I open a new terminal tab, I'm being nagged to change my mind about using the LTS release!

I've had to disable the POWERSHELL_UPDATECHECK for my sanity, but what I really want is to set it to "LTS"

Proposed technical implementation details (optional)

When a user is on an LTS release, only nag if they are not on the latest LTS.

When a new LTS release comes out, notify about the LTS update, and casually remind us of the other upgrade options.

When a LTS release is end-of-life (and there's a new major (minor) LTS version) then you should make the nag specifically about that and make it very clear what the current LTS release is.

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the implementation of POWERSHELL_UPDATECHECK and reading how the current version check decides when to notify. Define the LTS and latest-release cases from the issue, then verify that users on the latest LTS are not repeatedly nagged while outdated LTS users receive an LTS-focused notification.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, powershell
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.