Update freshness and remove v1.x configs #324
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit be83898: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
This PR updates documentation freshness dates and removes deprecated PowerShellGet v1.x configuration entries to streamline the documentation structure. The changes also include editorial improvements to enhance clarity and consistency across the documentation.
Changes:
- Updated freshness dates from outdated timestamps to 01/28/2026 in getting-started.md and faqs.yml
- Removed all PowerShellGet v1.x configuration entries from docfx.json and updated moniker ranges
- Applied editorial improvements and grammar fixes to getting-started.md and credential-persistence.md
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| powershell-gallery/docs-conceptual/powershellget/how-to/credential-persistence.md | Fixed grammar: changed "show" to "shows" and improved sentence flow by removing "Once you have provided the credential" |
| powershell-gallery/docs-conceptual/getting-started.md | Updated freshness date, removed deprecated manual download note, and applied numerous editorial improvements for clarity and consistency |
| powershell-gallery/docs-conceptual/faqs.yml | Updated freshness date from 06/12/2017 to 01/28/2026 |
| powershell-gallery/docfx.json | Removed all PowerShellGet v1.x build configurations, file metadata mappings, and updated moniker range from ">=powershellget-1.x" to ">=powershellget-2.x" |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| By default, `Install-Module` installs the module to `$env:ProgramFiles\WindowsPowerShell\Modules` | ||
| location by default, which requires an administrator account. If you add the `-Scope CurrentUser` |
There was a problem hiding this comment.
Redundant phrase 'by default' appears twice in the same sentence. The phrase 'location by default' should be simplified to just 'location' since 'By default' already appears at the beginning of the sentence.
| By default, `Install-Module` installs the module to `$env:ProgramFiles\WindowsPowerShell\Modules` | |
| location by default, which requires an administrator account. If you add the `-Scope CurrentUser` | |
| By default, `Install-Module` installs the module to the `$env:ProgramFiles\WindowsPowerShell\Modules` | |
| location, which requires an administrator account. If you add the `-Scope CurrentUser` |
| By default, `Install-Module` and `Install-Script` installs the most | ||
| current version of a package. To install an older version of the package, add the `-RequiredVersion` | ||
| parameter. | ||
| `Install-Module` and `Install-Script` installs the most current version of a package. To install an |
There was a problem hiding this comment.
The verb form 'installs' is grammatically incorrect here. Since the subjects are plural ('Install-Module and Install-Script'), the verb should be 'install' instead of 'installs'.
| `Install-Module` and `Install-Script` installs the most current version of a package. To install an | |
| `Install-Module` and `Install-Script` install the most current version of a package. To install an |
1 participant
PR Summary
Update freshness and remove v1.x configs
PR Checklist