GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Lack of compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11. · Issue #2152 · PowerShell/PSScriptAnalyzer

Lack of compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11. #2152

New issue
Copy link
New issue
Copy link
Open
#2228
Open
Lack of compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11.#2152
#2228
Copy link
Labels
Up-for-Grabs

Description

@ajn142
ajn142
opened on Jan 24, 2026
Issue body actions

Summary of the new feature

Add compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11, potentially other supported OS/PowerShell combinations as outlined by https://learn.microsoft.com/en-us/powershell/scripting/install/powershell-support-lifecycle

As a user, I would like to be able to leverage the PSUseCompatibleCommands check against profiles reflecting the current state of the OS and PowerShell, rather than only dated profiles reflecting unsupported OS and PowerShell versions. I am not proposing removal of any old profiles, just creation of new ones and relocation of unsupported ones to the optional directory.

Proposed technical implementation details (optional)

It would be nice if the process to generate these was added to the CI process, so that as Windows and PS Core versions move forward, new profiles are automatically generated.

What is the latest version of PSScriptAnalyzer at the point of writing

1.24.0

Reacted by HRXN

Activity

  1. ajn142 commented on Jan 24, 2026

    @ajn142
    ajn142
    on Jan 24, 2026
    Author
    More actions

    If the process outlined in #1657 is still accurate to generate profiles, I can potentially generate ones reflecting my current OSs and PowerShell versions and submit a PR, but I think implementing a CI process to build new profiles and retire old ones as optional would be a better overall fit. It's also unclear to me whether the process will include or bypass any modules I've written or installed beyond those available in base PowerShell, as I'd hate to contaminate the profiles with commands that aren't actually present on all installs.

    Reacted by HRXN
  2. Christoph Bergmeister (bergmeister)
    added
    Up-for-Grabs
    on Mar 31, 2026

  3. bergmeister commented on Mar 31, 2026

    @bergmeister
    Christoph Bergmeister (bergmeister)
    on Mar 31, 2026
    Collaborator
    More actions

    Yes, you can create your own profiles, we'd be happy to accept a PR for it. Preferably from an image that is used in GitHub Actions or Azure DevOps.

    Reacted by ajn142
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Up-for-Grabs

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions
      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.